|
From: | C K Wu |
Subject: | Re: [Phpgroupware-users] CK-ERP v.0.8.1 released |
Date: | Fri, 30 Jul 2004 22:21:49 +0800 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510 |
Hi, Brian,
Systemwide unique id means unique across all transactions. Say, a newly inserted customer record gets id 123, the next inserted invoice gets id 124, the next timesheet gets id 125, so on and so forth. As far as I can tell, addressbook only maintains id uniqueness within individual type of transaction, ie no organisation record could have duplicate id, but a personYou know I like ck-ledger, but the inability to still not use the phpgw addressbook table directly causes me concern. I know that any parallel contact storage system that relies on a sync mechanism is bound to encounter occasional problems. Perhaps it is due to my misunderstanding of how the "systemwide unique id" works
record can have the same id as an organization record.
One of the enhancement with CK-ERP is to use standardised table prefix. The default prefix is "ck_". But the system implementer could change it to whatever he/she prefers. But since it is a system crashing modification if made post implementation, the prefix is embedded in the script, ckapi.inc.php, and script modification is required to effect the change.I know that the existing addressbook has a hook to allow other apps to prevent deletion of addressbook contacts and I know that the addressbook system does use a unique id for each of it's entries .. so I don't nderstand the problem Could you explain it more please? Secondly, the version that I am currently running does not have "phpgw_" preceding the table names, does the current version?
Cheers, CK
_______________________________________________ Phpgroupware-users mailing list address@hidden http://lists.gnu.org/mailman/listinfo/phpgroupware-users
[Prev in Thread] | Current Thread | [Next in Thread] |