Incremental IDs ---> Global / Unique IDs

Next topic

Author	Message
Aldo Bucchi	Sunday 06 March 2005 3:03:23 pm Hi all, One of the reasons we have dropped eZp for major projects is the use of simple incremental IDs within the system, which leads to general portability problems and a terribly problematic Dev / Staging / Production workflow. Is the implementation of a Unique Identifier system considered in eZp's roadmap?
Łukasz Serwatka	Sunday 06 March 2005 10:43:18 pm Hi Aldo, In eZ publish you can use Identifier datatype where you define start value and incremental value. Every object of class can have own unique ID. More about datatypes here http://ez.no/ez_publish/documentation/incoming/appendices/appendix_c_ez_publish_datatypes Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Aldo Bucchi	Monday 07 March 2005 10:07:24 am mmh... but within the data model all PKs and FKs still use the simple incremental ID, right?

Author

Message

Sunday 06 March 2005 3:03:23 pm

Hi all,

One of the reasons we have dropped eZp for major projects is the use of simple incremental IDs within the system, which leads to general portability problems and a terribly problematic Dev / Staging / Production workflow.

Is the implementation of a Unique Identifier system considered in eZp's roadmap?

Łukasz Serwatka

Sunday 06 March 2005 10:43:18 pm

Hi Aldo,

In eZ publish you can use Identifier datatype where you define start value and incremental value. Every object of class can have own unique ID. More about datatypes here
http://ez.no/ez_publish/documentation/incoming/appendices/appendix_c_ez_publish_datatypes

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Aldo Bucchi

Monday 07 March 2005 10:07:24 am

mmh... but within the data model all PKs and FKs still use the simple incremental ID, right?

eZ debug

Timing:	Jan 30 2025 21:33:49
Script start
Timing:	Jan 30 2025 21:33:49
Module start 'layout'
Timing:	Jan 30 2025 21:33:49
Module start 'content'
Timing:	Jan 30 2025 21:33:49
Module end 'content'
Timing:	Jan 30 2025 21:33:49
Script end

Main resources:

Total runtime	0.0213 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0044	588.1563	151.2109
Module start 'layout'	0.0044	0.0033	739.3672	220.6875
Module start 'content'	0.0077	0.0121	960.0547	997.8359
Module end 'content'	0.0198	0.0015	1,957.8906	29.9922
Script end	0.0213		1,987.8828

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	12.1372	14	0.0002
Check MTime	0.0011	5.2318	14	0.0001
Mysql Total
Database connection	0.0006	2.9796	1	0.0006
Mysqli_queries	0.0019	8.7957	3	0.0006
Looping result	0.0000	0.0425	1	0.0000
Template Total	0.0010	4.8	1	0.0010
Template load	0.0008	3.6733	1	0.0008
Template processing	0.0002	1.0960	1	0.0002
Override
Cache load	0.0005	2.4601	1	0.0005
General
dbfile	0.0002	0.9831	8	0.0000
String conversion	0.0000	0.0235	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs