On Apr 8, 2010, at 8:58 PM, Sylvain Pointeau wrote: > You will probably end-up with a de-synchronized C++ version compared to the > Java version, > plus a constant effort to making it up-to-date.
You're right, but I don't have a better solution. I'm hoping if I can get the core work done then other guys part of the H2 effort can help keep the code in-sync over time. > just a little question for your needs, why not using sqlite? I studied the source code to SQLite and spent time conversing on its mailing list. I actually started trying to use it. However, the source code to SQLite is poorly architected and its development team has no clue when it comes to concurrency. If you ask about concurrency, the standard response is "threads are evil." I made an effort to work around its limitations. I finally gave up when I discovered that there was no way for me to maintain referential integrity using "INSERT OR REPLACE" (http://www.mentby.com/Group/sqlite-users/plans-for-completion-of-insert-or-replace-into.html) and I went looking for a better solution. Those guys spend more time worrying about netiquette than they do the deficiencies in their design. They may have fixed the issue by now, but the fact that they would ship a feature that didn't maintain referential integrity and the fact they have no clue how to properly handle concurrency led me conclude the project was good a good place to invest my resources. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
