On Wed, Jun 27, 2007 at 09:24:49AM +0300, Hannu Valtonen wrote:
> >Why do you need one
> In my case I have a large number of foreign keys in a table, which need
> to be updated frequently.
Alas, the high-level API of SQLObject is not well-suited for frequent
mass-updates. Use low-level API
Oleg Broytmann kirjoitti:
>
>> And also, what's the recommended workaround?
>>
>
>Why do you need one
In my case I have a large number of foreign keys in a table, which need
to be updated frequently. The amount of SQL queries this generates when
using .set() really eats up quite a bit of
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 i
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, w
