I think the ANSI SQL standard is that the column name should be empty. Any
other behavior is unportable. Nothing wrong with a mention in the DBI docs
that authors writing portable DBI programs should avoid using the
driver-dependent names of unaliased derived expression columns.
On Fri, Jan 29,
te:
> On Thu, 28 Jan 2010 11:59:16 -0500, Erik Aronesty
> wrote:
>
> > Just use the *_arrayref versions for multiple fields with the same name
> > instead of hashref or slice{}
>
> That is what I've shown. Bind_columns () or aliasing also works.
>
> > You
Just use the *_arrayref versions for multiple fields with the same name
instead of hashref or slice{}
You can't reliably refer to fields by name if they overlap.
On Tue, Jan 19, 2010 at 4:04 PM, Martin J. Evans
wrote:
> Hi,
>
> Is there anything special a subclassed DBI module (DBIx::Log4perl in
> this case) needs to do for the clone method?
>
> The DBI docs currently say "The clone method duplicates the $dbh
> connection by connecting with the same parame
Amalgamation what the SQLite maintainers recommend, and it's the
most portable, etc. So this is the right choice.
Also, given the way SQLite is maintained (backward compatibility is fairly
strict, they jump through hoops in their API to make it so), bundling
is fine, and is intended by the design
> >> I do Perl and C and offer some help.
>
> Same here. I feel reasonably at home both in C and Perl, and I've
> written some simple XS code. I don't have any experience with DBI,
I will also do what I can to help, if anyone wants it. Also, is there
a repository anywhere?
It's not documented i
