As Scott mentions there are many parts of the OFBiz data model (and
associated business logic) that use a Timestamp within database
tables/entities as a primary-key.
Another example: If you are using any of the content management logic
(blog, content publication and RSS feed come to mind) you could have
issues.
Even business logic as seemingly trivial as allowing a user to have
multiple shipping addresses (see the PartyContactMechPurpose entity) is
effected since a Timestamp is used as part of the fields that make up
the primary-key. FYI - I've seen this one in action. It wasn't
immediately obvious what was going on until I looked directly in the
database and saw the data.
Regards,
Ruth
On 6/25/12 10:12 AM, Scott Gray wrote:
It can also be a problem in tables like InventoryItemStatus or basically
anywhere in the system that depends on being able to retrieve the latest record
when it's possible for two records to have been created within the same second.
Also anywhere that depends on a timestamp as part of the primary key and
possible that similar records will be created within the same second
(ProductAverageCost is another one like ServerHit). And in general losing that
millisecond precision can make it difficult at times to know the order in which
a set of actions took place when looking through the data.
Regards
Scott
On 24/06/2012, at 2:10 PM, Brett Palmer wrote:
The only place I have found this to be a problem is in the server hit
entity. The server hit functionality is configurable. We disable that
functionality. We write custom applications using the ofbiz framework and
don't do a lot of ecommerce apps so its not a problem for us.
Brett
On Jun 22, 2012 11:48 PM, "Sanjeev Gupta" <[email protected]> wrote:
Thanks Bertt
How do you manage with the timestamp problem mentioned by Ruth.
SkipDever
Is replication native in 9.1 or though add-on components ?
-----
Rgds
Sanjeev
www.sanjeevg.com
@sanjeevgcom
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Ofbiz-with-MySQL-or-PostgreSQL-tp4633893p4633954.html
Sent from the OFBiz - User mailing list archive at Nabble.com.