On Fri, Mar 07, 2003 at 04:28:33PM -0800, Michael Peppler wrote:
On Fri, 2003-03-07 at 14:15, Tim Bunce wrote:
I'd appreciate a summary of which drivers support some form of
``last insert id'' and details of the interface they provide.
Specifically...
via an attribute or method?
On Sat, Mar 08, 2003 at 09:27:17AM -0500, Steven N. Hirsch wrote:
Tim,
I don't know if these items have been corrected in 1.35, since I cannot
find it on any of the CPAN mirrors. Unless this is applied, proxy will
not even pass regression tests due to compile errors:
All in except the
Tim Bunce wrote:
I'd appreciate a summary of which drivers support some form of
``last insert id'' and details of the interface they provide.
Specifically...
via an attribute or method?
at the sth or dbh level, or both?
any other details that might be relevant...
On Fri, Mar 07, 2003 at 11:12:00PM -0800, Jonathan Leffler wrote:
Tim Bunce wrote:
I'd appreciate a summary of which drivers support some form of
``last insert id'' and details of the interface they provide.
Specifically...
via an attribute or method?
at the sth or dbh level, or
Tim Bunce wrote:
On Sat, Mar 08, 2003 at 11:45:04AM +1100, Stas Bekman wrote:
Tim Bunce wrote:
p.s. I'm hoping DBI 1.35, which I've just released, will be fairly
stable and I can aim to put new things like this, and 'take_imp_data'
for Stas, into development releases leading up to a DBI 1.36.
Just a quick question on the topic. How far are you willing to go (or
willing to let DBD authors go) to support the API you're planning? For
example, Postgres has a SERIAL psuedo-type that really just creates a
sequence behind the scenes for you. I currently get the last insert id
using DBD::Pg
while building DBI-1.35 with blead-itreads perl I get:
cc -c -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBUGGING
-fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/usr/include/gdbm -g -DVERSION=\1.35\ -DXS_VERSION=\1.35\ -fpic
Tim Bunce wrote:
On Thu, Feb 27, 2003 at 03:04:36PM +1100, Stas Bekman wrote:
As I was looking through DBI.xs, I've noticed that dbi_get_attr_k is a very
long if/elseif flow. Wouldn't converting it to use switch(*key) (on the
first letter) make things a bit faster? Or is the Perl overhead so
Tim Bunce wrote:
On Fri, Mar 07, 2003 at 11:12:00PM -0800, Jonathan Leffler wrote:
Tim Bunce wrote:
I'd appreciate a summary of which drivers support some form of
``last insert id'' and details of the interface they provide.
Specifically...
via an attribute or method?
at the sth or
