Hi, The way I understand it, the reason for a single .set() to turn into multiple SQL queries is that when it has a "non-plain" type in the class, i.e. in my case multiple foreign keys.
Is this really the expected behaviour or is this a bug that's going to be fixed in later versions? And also, what's the recommended workaround? Create the proper SQL statement with sqlbuilder and then execute it? Also, do I have to flush sqlobject cache after doing so or does it detect db changes on it's own somehow? Hannu Valtonen / Ormod | [EMAIL PROTECTED] | http://www.niksula.cs.hut.fi/~hjvalton/ | ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
