On Sat, 2011-12-17 at 16:31 +0100, Benoît Minisini wrote:
> Hi,
>
> I have factorized your optimization and the code from the field_info
> function, and put it in revision #4280.
>
> Can you try it and check that I didn't break everything? And that
> optimization is always there of course!
>
>
Le 13/12/2011 21:58, Bruce Bruen a écrit :
> On Tue, 2011-12-13 at 06:08 +0100, Benoît Minisini wrote:
>
>
>>
>> Cool optimization apparently...
>>
>> Can you send me your code as an attachment so that I can open it
>> directly in an editor to check it?
>>
>> Thanks in advance!
>>
>> --
>> Benoît M
By the way, here is the log from my test harness for an "Update" cycle
(which changes a single column in a 46 column table and then undoes that
change).
The relevant lines are those marked "<< Connection.Edit"
Bruce
> Using repo gb.db.postgresql Main.c
T
Le 12/12/2011 09:01, Bruce Bruen a écrit :
> Hi Benoit,
>
> I was tracing through the postgresql library trying to figure out why
> some tables would add, update or delete single rows in milliseconds and
> others took "seconds".
> I found that the table_init function in gb.db.postgresql Main.c is
>
Le 12/12/2011 09:01, Bruce Bruen a écrit :
> Hi Benoit,
>
> I was tracing through the postgresql library trying to figure out why
> some tables would add, update or delete single rows in milliseconds and
> others took "seconds".
> I found that the table_init function in gb.db.postgresql Main.c is
>
Hi Benoit,
I was tracing through the postgresql library trying to figure out why
some tables would add, update or delete single rows in milliseconds and
others took "seconds".
I found that the table_init function in gb.db.postgresql Main.c is
calling the field_info function for each and every colu
