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" <subscr...@sanjeevg.com> 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. >>
