Thank you Werner for your response. I'm going to try the stuff with lazy loading afterwards, here is the issue about db-locking:
On Saturday 29 May 2004 10.33, Werner Guttmann wrote: > On Sat, 29 May 2004 00:17:15 +0200, Stefan Frank wrote: > >Hello everybody > > (...) > > > >Well the next point is much more important. In the documentation is only > >written that database-locking works with Oracle and Sybase. But it is > > nowhere mentioned that it also works with PostgreSQL. But on the other > > hand in the JDO-FAQ it is written, that PostgreSQL supports the main > > functions of Castor. > > Can you please point me the exact place of this, and I will amend the docs > accordingly. JDO FAQ: <-------------------------------------------------------------------------------------------------> http://www.castor.org/jdo-faq.html#Which-Open-Source-database-is-supported-better%3F Which Open Source database is supported better? --------------------------------------------------------- For now only with PostgreSQL 7.1 and SAP DB you get a full set of Castor features. Other Open Source databases don't support select with write lock, so db-locked locking mode doesn't work properly (it works in the same way as exclusive locking mode). All other Castor features are supported with MySQL, Interbase, InstantDB and Hypersonic SQL. <-------------------------------------------------------------------------------------------------> If I understand the first paragraph correclty, PostgreSQL + Castor supports db-locking. Well, and thats true in a ceratin way: As I mentioned I can lock objects, that have no references to other objects. But if there are, and theres a null-Reference, it comes to the nullable OUTER JOIN in Postgre... Maybe I misconfigured something? ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-user
