Mike,

From a post the other day, David pointed out that only MS and VistaDB have built in concurrency. The latest build mentions concurrency update/delete for Oracle (Enhanced Oracle Stored Procedure Templates - Concurrency Update/Delete ). Can this ability be added for MySQL? 

 

 

 

While automated concurrency handling via the timestamp column is only true for SQL Server and VistaDB, we added concurrency handling to Oracle from the very first official release. This maintenance release just tweaked it.

http://www.entityspaces.net/blog/2006/03/20/OracleSequencesAndConcurrencyHandling.aspx

Adding concurrency handling to MySQL is on the agenda, but still no official date. It most likely will not be automated using a timestamp column, but be an EntitySpaces specific implementation, similar to the Oracle design. You would add a large integer column in your table, and tell EntitySpaces to use it for concurrency from within MyGeneration's User Meta Data. Unfortunately, that entails some non-trivial changes to the EntitySpaces MySQL provider and stored procedure templates, and thorough testing.

---

David Neal Parsons
www.entityspaces.net

When the GUIDs are looked at in MySQL after the maintenance release can this maybe also be set as an item to review. I am trying to setup the ability to be as compatible as possible with MS SQL, MySQL and VistaDB for allowing different databases to be used.

 Thanks

Would this be a difficult task or is it fairly straight forward?

Again, just looking for compatibility between VistaDB, MySQL, and MS SQL.

Thanks

We are taking a good look at MySQL concurrency. I was talking to David last Wednesday during out meeting about it. MySQL like Guids doesn't have a great solution for concurrency, but we can make it work.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License