Thanks, but that's already in the next release. I hope to work on
actually making a release within the next week or so.
Tim.
On Wed, Mar 21, 2001 at 09:34:15PM -0500, Mark Stosberg wrote:
Hello! First, thanks to you all for your work on DBI. I use it
frequently and find it well put
On Thu, Mar 22, 2001 at 05:05:36PM +0100, Steffen Goeldner wrote:
Tim Bunce wrote:
I'd be interested to know what the Oracle ODBC driver returns for
various forms of Oracle NUMBER and happiest to do the same in DBD::Oracle.
Even, if the driver is very ugly? We have the chance to
make
On Mon, Mar 26, 2001 at 11:37:57PM -0500, Chip Turner wrote:
Hey Tim,
The need to have true OCI bound arrays for DBD::Oracle has come up,
and it looks like I get the fun job of implementing them. Basically,
this will allow DBD::Oracle to do something the DCOracle python
library does.
I'm not keen to add any prepare-wrappers or similar till the new prepare
stuff is in. But meanwhile they can happily live as DBIx::* extensions.
Tim.
On Fri, Mar 30, 2001 at 11:04:30AM -0800, Steve Shreeve wrote:
Tim,
At 04:43 PM 3/30/2001 +0100, you wrote:
It gives me great pleasure to
Ah, well spotted! Many thanks.
Tim.
On Mon, Apr 02, 2001 at 12:38:25PM -0400, T.J. Mather wrote:
I think I might have found a bug with the new selectrow_hashref feature of
DBI under mod_perl using Apache::DBI. When I attempt to use
selectrow_hashref, I get the following error:
Can't
Patches welcome :)
Tim.
On Tue, Apr 10, 2001 at 10:53:58AM +0200, Steffen Goeldner wrote:
Will the upcoming DBD::Oracle support attributes for table_info?
E.g.:
$sth = $dbh-table_info({ TABLE_SCHEM = 'SCOTT' });
Steffen
numerating things by having
one field be '%' and the others being null - but we can ignore that for now.
On Thu, Apr 12, 2001 at 03:30:42PM +0200, Steffen Goeldner wrote:
Tim Bunce wrote:
Patches welcome :)
Here our proposal:
sub table_info {
my($dbh, $attr) = @_;
How does it compare with DBD::Multiplex?
Tim.
On Mon, Apr 16, 2001 at 11:57:53AM -0500, Brian Drawert wrote:
HI!
I have been working on a new DBI-DBD module called DBD::HARD. The HARD
stands for High Availability and Replication Driver. It works very
similar to DBD::Proxy and DBI::Proxy
Great! I was hoping someone would do this.
Any chance you could rename it DBD::LDAP?
Tim.
p.s. I'd like to see a create table ... statement added that optionally
doesn't try to write a file - just defines an in-memory definition.
On Wed, Jun 06, 2001 at 02:27:08PM -0400, [EMAIL PROTECTED]
Maybe I'm not thinking straight but... I can't think of any reason for
primary_key_info to return different values for TABLE_CAT, TABLE_SCHEM,
or TABLE_NAME than the explicit single value specified as input.
Is that right?
Why then does the ODBC SQLPrimaryKeys API return those values in the
On Tue, Jul 10, 2001 at 10:00:02AM +0200, Steffen Goeldner wrote:
Tim Bunce wrote:
Also I think I'd prefer not using %attr for the TABLE_CAT, TABLE_SCHEM,
or TABLE_NAME. Seems too verbose. (I appreciate you were copying the
earlier table_info() precedent).
Thus:
$dbh-primary_key
On Tue, Jul 10, 2001 at 01:40:01PM -0400, [EMAIL PROTECTED] wrote:
Tim Bunce [EMAIL PROTECTED] wrote:
On Tue, Jul 10, 2001 at 10:00:02AM +0200, Steffen Goeldner wrote:
Tim Bunce wrote:
Also I think I'd prefer not using %attr for the TABLE_CAT, TABLE_SCHEM,
or TABLE_NAME
Read the Apache::DBI docs: it disables the disconnect method.
Tim.
On Fri, Jul 13, 2001 at 01:56:08PM +0100, Jules Beeston wrote:
We are using Apache mod_perl, DBI and DBD::Sybase to connect to our Sybase
db.
Even though we are opening connections and then closing connections the
TCP/IP
Umm, guess you can tell that I didn't have time to test it much :)
Tim [at the perl conference].
- Original Message -
From: H.Merijn Brand [EMAIL PROTECTED]
To: Tim Bunce [EMAIL PROTECTED]
Cc: DBI developers [EMAIL PROTECTED]
Sent: Monday, July 23, 2001 11:00 PM
Subject: Re: ANNOUNCE
Does anyone know of any DBI drivers that are implemented in XS (ie C) that
do not use the Driver.xst template file provided by the DBI?
Tim.
Arnold
- Forwarded message from Scott R. Godin
[EMAIL PROTECTED] -
From: Scott R. Godin [EMAIL PROTECTED]
To: [EMAIL PROTECTED] (Tim Bunce)
Subject: Re: ANNOUNCE: DBI_Talk5_2001.tar.gz
References: [EMAIL PROTECTED]
Organization: Laughing Dragon Services
User-Agent
On Tue, Aug 07, 2001 at 12:51:54PM -0700, Jonathan Leffler wrote:
On Sun, 5 Aug 2001, Jonathan Leffler wrote:
Tim Bunce wrote:
On Thu, Jan 04, 2001 at 02:09:53PM +0100, H.Merijn Brand wrote:
On Wed 01 Aug 2001 17:28, Tim Bunce [EMAIL PROTECTED] wrote:
Does anyone know of any DBI
On Sun, Aug 12, 2001 at 10:50:35PM -0700, Aaron Harsh wrote:
Tim,
I've recently become infatuated with Ruby, but I'm disturbed by the
primitive nature of its Oracle module. I suspect I could get pretty
far by ripping off your DBD::Oracle code, but I'd like to get your
blessing before I do
On Fri, Aug 10, 2001 at 07:34:58PM +0100, Nick Gorham wrote:
Jeff Urlwin wrote:
Have you tried building UnixODBC recently? (I've never tried so I
can't comment.)
Not recently, but it was painfully slow on my machine. It builds a lot of
individual files and takes a lot of time. I
Thanks!
It occurs to me that it would be nice if we could treat an undef
$schema as meaning the 'current' schema. But I don't know if it's
possible to find out the current schema in Oracle (ie after a possible
'alter session set current_schema=...'). Do you?
Tim.
On Thu, Aug 23, 2001 at
On Wed, Aug 22, 2001 at 04:58:43PM -0400, Jeff Urlwin wrote:
All -- I think I've got most, if not all the patches except the array
binding in now.
I have bind_param_inout in DBD::ODBC working for Oracle's ODBC driver --
however, I have found a problem, where I can't bind a null (undef).
Thanks!
Sadly the whole thing is a bit of a mess on the DBI side where old
names have changed values (like SQL_LONGVARCHAR was -1 now 12).
I think I need to 'bite the bullet' and just change/add them to
match the new standard. There may be some knock-on effects for
drivers and applications that
On Thu, Aug 30, 2001 at 08:08:57AM +0200, H.Merijn Brand wrote:
On Wed 29 Aug 2001 21:57, Tim Bunce [EMAIL PROTECTED] wrote:
file: $CPAN/authors/id/T/TI/TIMB/DBD-Oracle-1.09.tar.gz
size: 171660 bytes
md5: f37850230a66b7a0b3240b9667fbf812
After over a year since the last
Thanks!
Tim.
On Mon, Sep 03, 2001 at 01:06:23PM +0100, [EMAIL PROTECTED] wrote:
I think this could be considered a bug in DBD::AdabasD or in the proxy
server code.
DBI::ProxyServer::st::fetch() calls fetchall_arrayref(). This can
cause and infinite recursion and indeed does so with
Such releases could, and probably should, go out via CPAN using a
version number containing an underscore (so they won't be indexed).
Thus:
DBD-ODBC-0.32_01.tar.gz
Just set the VERSION (in Makefile.PL) or $VERSION (in ODBC.pm) like that
and MakeMaker and PAUSE will do the right thing.
On Wed, Sep 19, 2001 at 09:18:38AM +0200, Steffen Goeldner wrote:
Tim Harsch wrote:
Forgive me for listening in as I don't actually design any DBD modules. But
from a user standpoint, I am probably one of the few individuals you will
find that actually has both a PK and a UNIQUE
On Thu, Sep 20, 2001 at 11:55:55AM -0700, Jonathan Leffler wrote:
Moved to dbi-dev as this is getting much more like a dev issue than
a general dbi-users issue.
On Thu, 20 Sep 2001, Tim Bunce wrote:
On Wed, Sep 19, 2001 at 05:49:26PM -0700, Jonathan Leffler wrote:
On Wed, 19 Sep 2001, Tim
On Thu, Sep 20, 2001 at 03:00:24PM -0600, Robert Wyrick wrote:
I just joined the group and am assuming this is the correct place to post a
patch. Please excuse my ignorance if I am wrong...
It's a good place - and thanks.
This patch makes DBD::Oracle handle TIMESTAMP WITH TIME ZONE columns.
On Sun, Oct 21, 2001 at 12:55:31PM -0700, Terrence Brannon wrote:
On Wednesday, October 17, 2001, at 02:48 AM, Tim Bunce wrote:
The module I propose to develop (the second RFC of this email), makes
it
clear why this would be useful.
Er, actually it's not very clear to me.
all I
On Mon, Oct 22, 2001 at 09:01:30AM +0200, Wiedmann, Jochen wrote:
I could not figure this out because fetchrow_hashref must be
written in
C and not Perl
There is no reason for writing fetchrow_hashref in C. Just try.
I want to know if
fetchrow_hashref calls fetchrow_arrayref
On Sun, Oct 21, 2001 at 03:12:01PM -0700, Jason W May wrote:
I'm working on a module that I hope will provide a similar function for SQL
code that the various templating modules provide for HTML generation.
The goal is to move SQL code entirely out of the Perl, and to provide a very
On Mon, Oct 22, 2001 at 04:42:18PM -0500, Michael A Chase wrote:
DBI is open source. That includes the C source code. Look in the files
with .xs and .c extensions.
And .xst - Driver.xst is going to be growing in importance soon.
I expect it to be the home of a new version of
On Sun, Oct 21, 2001 at 07:23:52PM -0700, ivan wrote:
DBIx:: is appropriate. DBI:: is not. It seems like you should use SQL::
if you just work with abstract SQL statements (which the user then passes
to their database or uses in some other way), and DBIx:: if you'll
actually be talking to
On Tue, Oct 23, 2001 at 11:25:23AM +0200, H.Merijn Brand wrote:
On Tue 23 Oct 2001 02:03, Tim Bunce [EMAIL PROTECTED] wrote:
On Mon, Oct 22, 2001 at 04:42:18PM -0500, Michael A Chase wrote:
DBI is open source. That includes the C source code. Look in the files
with .xs and .c
You won't get far without providing a strong case for *why*.
Tim.
On Tue, Oct 23, 2001 at 11:17:31AM +0100, Simon Oliver wrote:
I wish to propose a patch for DBI. I have patched in the methods but
don't know how to patch in new DBI attributes?
Please can you advise how to add new
On Tue, Oct 23, 2001 at 03:28:04PM +0100, Simon Oliver wrote:
Tim Bunce wrote:
You won't get far without providing a strong case for *why*.
I have tried on a number of occasions but got no response so I decied to
have a ago a creating a working, patched version and offering it up
On Thu, Nov 15, 2001 at 11:52:44AM +0100, Steffen Goeldner wrote:
Metadata routines are used to obtain information about
- drivers and data sources
- the implementation
- the catalog
The following table shows these routines defined by SQL/CLI,
ODBC and DBI:
SQL/CLI ODBC
Done (actually changed to M=Mature :)
Thanks.
Tim.
On Thu, Nov 15, 2001 at 07:59:51PM +0100, Honza Pazdziora wrote:
Hi,
CPAN still lists DBI module as amcO. Shouldn't the status be
changed to RmcO?
--
Honza
On Fri, Nov 23, 2001 at 03:16:32PM +0100, Steffen Goeldner wrote:
Tim Bunce wrote:
(see http:[EMAIL PROTECTED]/msg00499.html)
[And I'd ideally like to be able to detect and warn about misspelt
SQL_ attributes. And I'd also like to make it easy to map the names
into their official
It's on my list to look into soon. Thanks.
Tim.
On Wed, Nov 14, 2001 at 10:45:55AM +0100, Polak Michal wrote:
Hello,
there is memory leaking somewhere. I think it is in DBI.
Please, try this source code (replace dbname, username and password,
please):
The dbi-dev list of not really the right place for driver support questions.
Please post those to dbi-users.
[And for dbi-dev list members, please redirect such emails over to
dbi-users rather than respond here. Thanks.]
Tim.
On Mon, Nov 26, 2001 at 04:34:36PM -0500, Wilson, Allen wrote:
Good
Please ask on the dbi-users list, not dbi-dev. Thanks.
On Tue, Nov 27, 2001 at 10:12:04AM -0500, Helen He wrote:
Hi, All
I am writting a perl script that retrieves data from remote oracle
database server. In order to let the script know the path of the remote
server, what variables
On Sat, Dec 01, 2001 at 01:19:47PM -0500, Thomas A.Lowery wrote:
This is a good idea. I'm wondering what other Defaults to allow for?
The attribute should be named 'ado_...', the underscore is part of
the driver-private name prefix.
Beware of the performance cost of all these extra little
On Fri, Nov 30, 2001 at 12:29:20PM +, Jacqui Caren wrote:
Tim,
I find myself writing a do_cached method quite often.
Given this should be identical to the do algorithm
except that prepare_cached is used, would you consider
addng do_cached to the DBI API?
I'm aware of the
On Mon, Dec 03, 2001 at 07:07:33PM +, Jacqui Caren wrote:
On Mon, 3 Dec 2001 17:20:24 +, Tim Bunce wrote:
On Sat, Dec 01, 2001 at 01:19:47PM -0500, Thomas A.Lowery wrote:
This is a good idea. I'm wondering what other Defaults to allow for?
The attribute should be named 'ado_
On Tue, Dec 04, 2001 at 08:00:15PM +0100, Flemming Frandsen wrote:
Tim Bunce wrote:
I'd rather not go that way (I don't like solutions that require
mangling the sql in odd ways).
Hmm, ok then.
I think I'd rather optionally ignore placeholders named ':old' and ':new'.
Also, I
[I'm replying to [EMAIL PROTECTED] as I think this is of general interest.]
On Thu, Jan 03, 2002 at 02:55:47AM -0600, Dave Rolsky wrote:
[... lots of good stuff about Alzabo ...]
I'm not sure how much this relates to DBI but I figured I'd point out that
A) I've at least thought about some
On Wed, Jan 09, 2002 at 09:57:27AM +, Simon Oliver wrote:
Jonathan Leffler wrote:
H, basically, I see what's going on. Informix only supports
delimited identifiers if the environment variable DELIMIDENT is set when
the connection is initiated, which will make this very
On Wed, Jan 09, 2002 at 09:41:28AM -0800, Michael Peppler wrote:
Tim Bunce writes:
On Wed, Jan 09, 2002 at 09:57:27AM +, Simon Oliver wrote:
Whether the DBD determines/sets this value on a per connection basis, when the
identifier_delimitor method is called or each time
even if they
require quoting (for dynamic applications, like db browsers).
c) er, anyone think of any others?
Tim.
On Wed, Jan 09, 2002 at 05:20:07PM -0800, Jonathan Leffler wrote:
On Thu, 10 Jan 2002, Tim Bunce wrote:
On Wed, Jan 09, 2002 at 09:41:28AM -0800, Michael Peppler wrote:
Tim
On Wed, Jan 09, 2002 at 09:54:07PM -0500, Rudy Lippan wrote:
If a database do not support quoting, wouldn't be up to the DBD driver to
complain loudly when someone tries to quote something, and otherwise just
be a no-op?
No need to complain. quote_identifier would just return the unquoted
Thanks. I'll get back to you after next week.
Tim.
On Thu, Jan 10, 2002 at 11:08:07AM +0100, Steffen Goeldner wrote:
Tim Bunce wrote:
On Mon, Nov 26, 2001 at 09:21:49PM +, Tim Bunce wrote:
On Mon, Nov 26, 2001 at 04:25:16PM +0100, Steffen Goeldner wrote:
On reflection I agree
I've discovered that if I run something like:
while (1) {
connect_cached
prepare_cached
execute
finish
sleep(10 seconds longer than the DBMS timeout)
}
Can you show me the actual code?
Then the system may leak ressources, with most drivers and setups you
will never notice;
The dbi-dev list is not for driver support issues. Use dbi-users.
Tim.
On Wed, Jan 16, 2002 at 11:47:17AM -0700, Jempty, George wrote:
I'm using a Windows2k/IIS/CGI program to report against Oracle data on a
Unix machine, the Oracle version on both client and server is 8.1.7. The
following
The dbi-dev list is not for driver support issues. Use dbi-users.
Tim.
On Thu, Jan 17, 2002 at 07:58:03AM -0600, Joe Reganato wrote:
Hello my name is Joe Reganato Jr.
my email address is [EMAIL PROTECTED]
I have a question/problem about dbi...
I am working with a db2 database ... It
On Fri, Jan 18, 2002 at 08:58:33AM +0100, Flemming Frandsen wrote:
Please enable trace and try to confirm that DESTROY is being called.
heh?
See the docs. Set the DBI_TRACE env var to something like 2=/tmp/dbitrace.log
Tim.
It would have to be a new method. Perhaps
bind_param_at_execute(...)
bind_param_lazy(...)
bind_param_ref(...)
The driver could just defer the actual bind till execute is called.
I might just be able to get the Driver.xst template code to handle that
automatically.
todo
On Sun, Jan 20, 2002 at 11:01:17PM -0800, Jonathan Leffler wrote:
Tim Bunce wrote:
I'd appreciate any input from driver authors who either:
a) set ChopBlanks on by default (which they probably shouldn't)
Not guilty (referring to DBD::Informix, of course). Is ChopBlanks
settable
On Sun, Jan 20, 2002 at 08:00:33PM -0800, Sterin, Ilya wrote:
-Original Message-
From: Tim Bunce [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 20, 2002 2:16 PM
To: Sterin, Ilya
Cc: [EMAIL PROTECTED]
Subject: Re: bind_param()
It would have to be a new method
On Mon, Jan 21, 2002 at 01:42:40PM -0800, Jonathan Leffler wrote:
[...]
Thanks, the examples helped explain where you're coming from.
I strongly recommend closing this conversation now. I've made all the
points I can make as clearly as I can make them, and I'm not having any
effect on
On Mon, Jan 21, 2002 at 05:57:51PM -0800, Jonathan Leffler wrote:
On Mon, 21 Jan 2002, Tim Bunce wrote:
Since DBI won't allow the application to tell us that it wants to use
quoted identifiers, we're stuck in a lose-lose situation.
To tell if the driver is going to quote identifiers
On Tue, Jan 22, 2002 at 10:20:42AM +0100, H.Merijn Brand wrote:
On Tue 22 Jan 2002 00:16, Jeff Urlwin [EMAIL PROTECTED] wrote:
Tim,
I'm against it. Reasoning: char (and nchar) columns are, at least in my
experience, PADDED by the DB. Varchar columns, typically, are not. Thus:
On Tue, Jan 22, 2002 at 05:39:27PM +0100, H.Merijn Brand wrote:
On Tue 22 Jan 2002 17:26, Tim Bunce [EMAIL PROTECTED] wrote:
On Tue, Jan 22, 2002 at 10:20:42AM +0100, H.Merijn Brand wrote:
On Tue 22 Jan 2002 00:16, Jeff Urlwin [EMAIL PROTECTED] wrote:
Tim,
I'm against
On Fri, Jan 25, 2002 at 08:39:40AM -0800, Jeff Zucker wrote:
Tim Bunce wrote:
Please make SQL92 the default as far as possible.
That is *always* my aim but I welcome people monitoring me on it since I
may make mistakes and since the standard is not always clear.
That means all
On Sat, Jan 26, 2002 at 05:23:19PM -0800, Tim Harsch wrote:
Could somebody please fix the pointers to the archives on the
symbolstone home page? The US list has not worked in I don't know how
long and the European one has moved and all you get is the new server's
home page. Thanks
Al tells
DBI 1.201 (and soon 1.21) have a new quote_identifier method.
The tables method should use this to quote the identifiers it returns.
The DBI now provides a default quote_identifier method that does
standard SQL quote_identifier quoting (using double quotes).
Great.
But there's a problem for
On Thu, Jan 31, 2002 at 11:05:25AM +0100, Steffen Goeldner wrote:
Tim Bunce wrote:
On Tue, Jan 29, 2002 at 02:36:54PM -0800, Jeff Zucker wrote:
* The $info_type parameter is an integer. These integers can be
found in the docs for ODBC or SQL/CLI
Yes.
or in the DBI
dbi-dev isn't the place to ask. Please post to [EMAIL PROTECTED] instead.
On Thu, Jan 31, 2002 at 06:34:50PM +, Abi Pothen wrote:
Hi,
I have installed FreeTDS and trying to access MS SQL Server (7 2000 ) from
Sun Solaris Unix box. I am using DBD:Sybase ( ver 0.91 ).
Everything is
On Fri, Feb 01, 2002 at 10:46:12AM -0800, Jeff Zucker wrote:
Tim Bunce wrote:
Umm, carrying on from there... move %get_info_constants into DBD::Oracle::GetInfo
and make get_info do:
So is this the way to do get_info() for DBD::CSV and DBD::AnyData?
Well it's certainly one way
On Mon, Feb 04, 2002 at 08:53:46AM +0100, Steffen Goeldner wrote:
Tim Bunce wrote:
Umm, carrying on from there... move %get_info_constants into DBD::Oracle::GetInfo
and make get_info do:
sub get_info {
my($dbh, $info_type) = @_;
require DBD::Oracle::GetInfo;
my $v
On Mon, Feb 04, 2002 at 09:45:08AM -0800, Jeff Zucker wrote:
The drivers could certainly try looking up $info_type in whichever
SQL::Statement they're using (giving it 'first refusal' to answer
any requests). SQL::Statement would only define values that are
appropriate to it.
If
On Tue, Feb 05, 2002 at 04:37:48PM +0100, Steffen Goeldner wrote:
+ sub sql_identifier_quote_char {
+ my $dbh = shift;
+ my $sth = $dbh-func('adSchemaDBInfoLiterals','OpenSchema');
+ while ( my $row = $sth-fetch ) {
+ return $row-[1] if $row-[0] eq 'QUOTE'; # XXX
Don't be surprised if you haven't heard of the Handlers attribute,
it's not documented. And don't bother finding out about it because
it's probably going away.
But I think I have mentioned it a couple of times and wanted to
check if anyone was using it for anything? And if so, what (so
I can
On Thu, Feb 07, 2002 at 11:13:22AM +0100, Steffen Goeldner wrote:
Tim Bunce wrote:
On Wed, Feb 06, 2002 at 09:48:54AM +0100, Steffen Goeldner wrote:
[...]
I'm not sure if we can cache *every* value. Is it possible that a DBMS
allows to change some properties at runtime (something
Ah, I've an idea what's caused that. Thanks!
Tim.
On Thu, Feb 07, 2002 at 10:26:07AM -0500, Jeff Urlwin wrote:
Tim,
I, accidentally had DBI_TRACE set to 1 in the environment and I get an
invalid pointer problem in DBI dispatch during t/preparse.t. I've traced it
to the following lines,
Please post to dbi-users not dbi-dev. Thanks.
Tim.
On Thu, Feb 07, 2002 at 05:31:01PM +, [EMAIL PROTECTED] wrote:
Hi,
First of all, excuse my grammar mistakes, because I'm spanish and I seldom
write in English.
We are trying to install DBD and DBI modules in HP-UX 11.0 and we have a
On Mon, Feb 11, 2002 at 12:36:59PM +0100, Steffen Goeldner wrote:
Tim Bunce wrote:
p.s. Steffen, any chance you could produce a chunk of code that'll
connect to a DSN (specified on the command line), query all the
get_info values and dump the results to stdout as a DBD::foo::GetInfo
On Fri, Feb 15, 2002 at 06:24:13PM +0100, Steffen Goeldner wrote:
Tim Bunce wrote:
p.s. Steffen, any chance you could produce a chunk of code that'll
connect to a DSN (specified on the command line), query all the
get_info values and dump the results to stdout as a DBD::foo::GetInfo
On Sun, Feb 17, 2002 at 01:28:30PM -0800, Jeffrey W. Baker wrote:
Aside: It seems that DBI is willing to call into the DBD implementation
to fetch (dbd_st_fetch) even on handles which have been invalidated by
disconnection. Should not these statement handles have Active marked
FALSE upon
On Wed, Feb 13, 2002 at 01:52:11PM -0800, Jonathan Leffler wrote:
I've been emulating a pseudo-SQL command, UNLOAD, in DBI and
DBD::Informix, and one of the messy parts is handling the mapping of
undef into an empty string so as not to get warnings with 'perl -w'.
I've also routinely
On Tue, Feb 19, 2002 at 10:41:37AM +0100, H.Merijn Brand wrote:
But have these functions not implemented?
- Place holders
Yes, in CVS, but SQLite doesn't support them, so it uses the hackish
method of splitting up the SQL on ? and re-joining it for execution with
the values in
On Thu, Feb 21, 2002 at 12:14:31PM +0100, Steffen Goeldner wrote:
Since DBI supports the SQL/CLI LOB datatypes
- SQL_CLOB and
- SQL_BLOB
and DBI supports the temporal datatype
- SQL_TYPE_TIMESTAMP
and DBD::Oracle has ora_server_version(), we could provide a more
specific
On Wed, Feb 13, 2002 at 10:58:34AM -0800, Jonathan Leffler wrote:
On Wed, 13 Feb 2002, H.Merijn Brand wrote:
On Wed 13 Feb 2002 02:02, Jonathan Leffler [EMAIL PROTECTED] wrote:
+=over 4
+
+*FIX ME* If there are statements 'active' when the $dbh is destroyed,
+does DBI arrange to destroy
On Wed, Feb 13, 2002 at 11:36:36AM -0800, Jonathan Leffler wrote:
Hi - another question:
The sample code for DBD::Driver::db::prepare starts:
sub prepare
{
my ($dbh, $statement, @attribs) = @_;
# create a 'blank' sth
my $sth = DBI::_new_sth($dbh, {
On Wed, Dec 31, 1969 at 08:58:45PM -0500, Terrence Brannon wrote:
Call me paranoid I have never ever had a database connection die
after I got it
However, I feel funny writing a book on coding Industry-Strength
DBI (co-authors welcome)
without being able to say and via this attribute or
Umm, here's another thought...
How about changing prepare_cached so it includes the caller() info
in the hash key by default. That way prepare_cached won't return
the same statement handle if called from two different places even
if the $statement is the same.
Tim.
On Wed, Feb 27, 2002 at
Yeap Thanks
Tim
ps Keep adding these to your 'jumbo patch' and I'll ask you for
the latest version of that once I get to work on DBD::Oracle again
Thanks
On Thu, Feb 28, 2002 at 03:30:12PM +0100, Steffen Goeldner wrote:
Steffen Goeldner wrote:
Tim Bunce wrote:
On Thu, Feb 21, 2002
On Mon, Mar 04, 2002 at 08:50:45AM -0800, Jeff Zucker wrote:
Tim Bunce wrote:
On Sun, Mar 03, 2002 at 12:41:54PM -0800, Jeff Zucker wrote:
$dbh-do(q/ CREATE TABLE x ( OOg INT, BOOg CHAR ) /);
$sth=$dbh-prepare(q/ SELECT boog FROM x /); #4 NO SUCH COLUMN
$sth=$dbh-prepare
All DBI driver authors need to change from
fprintf(DBILOGFP,
to
PerlIO_printf(DBILOGFP,
Tim
On Tue, Mar 05, 2002 at 03:45:30PM -0600, Dave Rolsky wrote:
DBI itself compiled fine, as did DBD::mysql, but then DBD::Pg gave me
this during make make test was fine, as was make
On Wed, Mar 06, 2002 at 03:19:34AM +0200, Jarkko Hietaniemi wrote:
On Wed, Mar 06, 2002 at 12:18:22AM +, Tim Bunce wrote:
All DBI driver authors need to change from
fprintf(DBILOGFP, ...
to
PerlIO_printf(DBILOGFP, ...
Tim.
Ouchie. Is there a dbi-authors mailing
On Wed, Mar 06, 2002 at 02:05:55PM +0100, H.Merijn Brand wrote:
On Wed 06 Mar 2002 11:46, Tim Bunce [EMAIL PROTECTED] wrote:
It would be very useful if as many people as possible could test
perl 5.7.3 and especially, for us here, get as many DBD drivers
tested as well. Perl 5.8
On Wed, Mar 06, 2002 at 08:05:47AM -0800, Jeffrey W. Baker wrote:
On Wed, 2002-03-06 at 03:41, Tim Bunce wrote:
On Wed, Mar 06, 2002 at 03:19:34AM +0200, Jarkko Hietaniemi wrote:
On Wed, Mar 06, 2002 at 12:18:22AM +, Tim Bunce wrote:
All DBI driver authors need to change from
On Wed, Mar 06, 2002 at 12:13:25PM -0800, Jonathan Leffler wrote:
Hi Tim,
DBI 1.21 has a use of fprintf(DBILOGFP in DBI.xs at line 2993.
--- DBI.xs.oldWed Feb 6 19:15:42 2002
+++ DBI.xsWed Mar 6 12:05:15 2002
-2990,7 +2990,7
/* default to method call via stash of
On Wed, Mar 06, 2002 at 03:04:51PM -0800, Jeff Zucker wrote:
Tim Bunce wrote:
On Mon, Mar 04, 2002 at 08:50:45AM -0800, Jeff Zucker wrote:
Hmm, I just checked the SQL92 standard and if I'm reading it correctly
the situation is ugly. Section 5.2.13 appears to say that a regular
Yeap, seems reasonable.
Tim.
On Wed, Mar 06, 2002 at 04:49:58PM -0800, Jeff Zucker wrote:
Tim Bunce wrote:
On Wed, Mar 06, 2002 at 03:04:51PM -0800, Jeff Zucker wrote:
It's from the PDF of SQL92 I purchased from www.ansi.org. But here's
the text:
13)
A regular
The official status is that it's okay in principle but I need to
think through the API because I want to be sure that the DBI can
provide transparent fallback behaviour if the driver doesn't support it.
That'll take time, especially as my attention is not turning to
DBD::Oracle (and Oracle::OCI
On Thu, Mar 07, 2002 at 04:59:41PM +, Tim Bunce wrote:
The official status is that it's okay in principle but I need to
think through the API because I want to be sure that the DBI can
provide transparent fallback behaviour if the driver doesn't support it.
That'll take time, especially
On Fri, Mar 08, 2002 at 09:32:56PM -0800, Ian Kallen wrote:
DBD::JDBC wants the SQL_BIGINT from DBI sql_types but alas, it's not
there. Is there a plan to remedy this?
It was removed in DBI 1.21. The perldoc DBI::Changes says:
Removed the definition of SQL_BIGINT data type constant as the
Thanks.
I think the DBI should follow ODBC where it differs from SQL/CLI
in areas where ODBC is not likely to change. This is probably
one of those places.
Tim.
On Fri, Mar 15, 2002 at 12:46:29PM +0100, Steffen Goeldner wrote:
Steffen Goeldner wrote:
P.S.: It seems I'll have TO DO
On Mon, Mar 18, 2002 at 12:05:28PM +0100, Steffen Goeldner wrote:
Tim Bunce wrote:
Thanks.
I think the DBI should follow ODBC where it differs from SQL/CLI
in areas where ODBC is not likely to change. This is probably
one of those places.
O.k., I dropped the first 'XXX
1 - 100 of 1441 matches
Mail list logo
