eZ and Oracle

Next topic

Author	Message
Marko Žmak	Wednesday 02 June 2010 3:42:04 am In my quest for the (holly grail) answer to the question "eZ Publish or Drupal?" I came accross this article: http://www.oracle.com/technology/pub/articles/pedros-drupal.html So I'm interested how would eZ deal with the issues described there, especially those pointed out in the "Where Are We Now?" chapter. -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
Gaetano Giunta	Wednesday 02 June 2010 1:51:54 pm Last time I checked (around 2007 iirc), drupal had no db-access-layer at all. There was some chat going on about adding oracle support, but it was not a trivial task. The blog linked from the article you mention is dead... On the eZ side: we have a full developed db access layer - on projects.ez.no a partner has published even a mssql connector! we have a fully working oracle connector, and we have had for a long time we have one of the most talented oracle coders in the php community, who matured experience participating to the adodb project, too (in case you do not get the joke: it's me!) we have paying customers on Oracle Or where you asking for real technical aspects of creating a cms that is portable between dbs? That would take a much longer answer... The starting point to gleam some info would be to look into the code of the ezoracle extension. But I might have laying around a slide set used to teach oracle-style to mysql coders if you are interested. Principal Consultant International Business Member of the Community Project Board
Chen Xiongjie	Thursday 03 June 2010 12:43:22 am LOL.:) " we have one of the most talented oracle coders in the php community, who matured experience participating to the adodb project, too (in case you do not get the joke: it's me!) " In addition, eZ has Oracle unit test support from this last alpha version(4.4.0 alpha2). -- Chen eZ Comments: http://projects.ez.no/ezcomments twitter: http://twitter.com/xiongjie
Bertrand Dunogier	Thursday 03 June 2010 1:35:52 am While it is true that our oracle implementation is now well tested and supported, I think some of the issues raised in the linked article can't be ditched just like that. The platform-neutral SQL part is one we have already discussed many times. Having an SQL language abstraction is one thing, data models and how each database is best used indeed is a complex matter. While our implementation works, and works fine, there is no doubt that the database schema isn't really optimized for Oracle. RDBMS "custom" features are mentioned here, and the abstraction indeed doesn't let us benefit from most of these specificities. Regarding the database structure and oracle specific implementations, I think Gaetano has covered this up pretty correctly, thanks to his huge experience with oracle. There probably is room for improvement, but I think we're on the right track here. Any comments on these specific points ? Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
Yannick Modah Gouez	Monday 30 May 2011 6:42:24 am " In addition, eZ has Oracle unit test support from this last alpha version(4.4.0 alpha2). " I never heard of that feature, could you please tell us more about it ?

eZ debug

Timing:	Jan 18 2025 02:02:10
Script start
Timing:	Jan 18 2025 02:02:10
Module start 'layout'
Timing:	Jan 18 2025 02:02:10
Module start 'content'
Timing:	Jan 18 2025 02:02:12
Module end 'content'
Timing:	Jan 18 2025 02:02:12
Script end

Main resources:

Total runtime	1.8442 sec
Peak memory usage	4,096.0000 KB
Database Queries	69

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0064	587.7891	152.6094
Module start 'layout'	0.0064	0.0032	740.3984	39.3984
Module start 'content'	0.0096	1.8330	779.7969	698.2656
Module end 'content'	1.8426	0.0016	1,478.0625	16.2031
Script end	1.8442		1,494.2656

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.1888	16	0.0002
Check MTime	0.0014	0.0769	16	0.0001
Mysql Total
Database connection	0.0008	0.0411	1	0.0008
Mysqli_queries	1.7745	96.2188	69	0.0257
Looping result	0.0008	0.0438	67	0.0000
Template Total	1.8069	98.0	2	0.9035
Template load	0.0020	0.1067	2	0.0010
Template processing	1.8049	97.8697	2	0.9025
Template load and register function	0.0001	0.0065	1	0.0001
states
state_id_array	0.0014	0.0779	1	0.0014
state_identifier_array	0.0014	0.0776	2	0.0007
Override
Cache load	0.0018	0.0976	35	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0344	5	0.0001
Fetch class attribute name	0.0018	0.0963	9	0.0002
XML
Image XML parsing	0.0043	0.2338	5	0.0009
class_abstraction
Instantiating content class attribute	0.0000	0.0007	9	0.0000
General
dbfile	0.0032	0.1714	36	0.0001
String conversion	0.0000	0.0006	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
4	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
5	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
8	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/li.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/li.tpl
1	content/datatype/view/ezxmltags/ul.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/ul.tpl
2	content/datatype/view/ezxmltags/quote.tpl	datatype/ezxmltext/quote.tpl	extension/ezwebin/design/ezwebin/override/templates/datatype/ezxmltext/quote.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 23 Number of unique templates used: 8

Time used to render debug report: 0.0001 secs