On Wed, Jun 27, 2007 at 12:50:32AM +0300, Hannu Valtonen wrote:
> 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?
It is expected. SQLObject executes one query for all non-plain setters
at once, and a query for every non-plain setter.
> And also, what's the recommended workaround?
Why do you need one?
> Create the proper SQL
> statement with sqlbuilder and then execute it?
Well, that can do.
> Also, do I have to flush
> sqlobject cache after doing so
Yes.
> does it detect db changes on it's own
> somehow?
No, there is no magic in SQLObject.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ [EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
