Hi,
"SELECT MAX(columnid)" is only a workaround, which of course isn't
multi-user-safe at all. This workaround is used for databases where no
other way to retrieve generated values is known - unfortunately there's
no (wide-spread enough) standard to retrieve the server-side generated
values afte
Le Vendredi 7 Juillet 2006 16:14, Frank Schönheit - Sun Microsystems Germany a
écrit :
> I see the potential for sharing code here, but I'm not sure whether a
> shared "first-level" driver lib would be the way to go. Reason is that
> some differences in the different implementations can only be
>
Hi Éric,
(hey, you just finally volunteer for implementing a new database driver
framework :)
> The KDE address book driver is split into two parts:
> ...
> So this framework is more or less general.
>
> I think that, if we redesign the drivers some day, it would be more efficient
> to group al
Hi Frank,
I'd like to share a few thoughts that occured to me while I was under the
shower (it always happens so for me, I don't know for you...).
The KDE address book driver is split into two parts:
- one DLL that loads the second DLL if certain conditions are met
(namely, KDE at run time
Hi Ross,
> In short, if I delete the original form control and replace it with a
> new one it works fine from then on. I should be satisfied that it's
> working now, but I'm interested in what happened to the original control
> to break it. Something in the original form control presumably went
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Ross,
Using tcpdump to compare the SQL commands sent from OOo to PostgreSQL, I
can see where the problem is occuring. When adding a new record via the
form, the INSERT includes the autosequencing column (sampleid), which
inserts a value
