On 15/03/12 10:16, Martin J. Evans wrote:
On 14/03/2012 10:20, Tim Bunce wrote:
On Wed, Mar 14, 2012 at 08:24:36AM +0100, H.Merijn Brand wrote:
On Tue, 13 Mar 2012 21:44:06 +, Tim Buncetim.bu...@pobox.com
wrote:
On Fri, Mar 02, 2012 at 03:11:17PM +, Tim Bunce wrote:
The second patch
multiple result sets
was more complicated than some people first thought and I guess that is why it
never really came to fruition. In particular:
http://www.nntp.perl.org/group/perl.dbi.dev/2004/03/msg3243.html
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
any DBIS stuff but to be sure I'd echo Merijn's
reply; if you could point out what to look for and an approach I'd happily
change any DBD I could run and provide patches for it (currently I have ODBC,
Pg, Oracle, CSV, SQLite, mysql and all those you get with DBI).
Martin
--
Martin J. Evans
On 14/03/12 10:37, Tim Bunce wrote:
On Wed, Mar 14, 2012 at 08:52:38AM +, Martin J. Evans wrote:
On 13/03/12 21:44, Tim Bunce wrote:
On Fri, Mar 02, 2012 at 03:11:17PM +, Tim Bunce wrote:
The second patch, which makes DBIS more efficient, is a lot more complex,
and more likely
On 14/03/12 11:37, Martin J. Evans wrote:
On 14/03/12 10:37, Tim Bunce wrote:
On Wed, Mar 14, 2012 at 08:52:38AM +, Martin J. Evans wrote:
On 13/03/12 21:44, Tim Bunce wrote:
On Fri, Mar 02, 2012 at 03:11:17PM +, Tim Bunce wrote:
The second patch, which makes DBIS more efficient
I've just uploaded DBD::ODBC 1.35 to CPAN.
This is the culmination of 7 development releases in the 1.34 chain and
is a significant release containing a lot of changes and enhancements.
As always I would like to thank everyone who has helped and especially
CPAN testers. The full list of
On 23/02/12 11:04, Tim Bunce wrote:
On Wed, Feb 22, 2012 at 08:40:09PM +, Martin J. Evans wrote:
I've applied Dave's patch and tested in on Windows with Perl 5.8.9
and it now compiles without errors.
Also the patch from Manoj Kumar is applied and this fixes gofer tests.
Great. Thanks
with either of these?
Tim.
p.s. Once these are fixed I'll probably release DBI 1.618 without the
DBIS change as I've not had time to consider that in the detail it needs.
I'll try and run through the machines I have again and take Merijn's response
into consideration too.
Martin
--
Martin J. Evans
On 22/02/12 08:22, Martin J. Evans wrote:
On 21/02/12 22:01, Tim Bunce wrote:
DBI 1.617_903 has a 100% pass rate on everything except MSWin32,
where there are three reports so far and 100% failure:
http://matrix.cpantesters.org/?dist=DBI%201.617_903;reports=1;os=mswin32
Result Id OS vers
On 22/02/12 08:55, Martin J. Evans wrote:
On 22/02/12 08:22, Martin J. Evans wrote:
On 21/02/12 22:01, Tim Bunce wrote:
DBI 1.617_903 has a 100% pass rate on everything except MSWin32,
where there are three reports so far and 100% failure:
http://matrix.cpantesters.org/?dist=DBI%201.617_903
On 22/02/12 11:09, Dave Mitchell wrote:
On Wed, Feb 22, 2012 at 10:04:45AM +, Martin J. Evans wrote:
DBI.xs(4291) : error C2275: 'SV' : illegal use of this type as an expression
C:\Perl\lib\CORE\perl.h(2243) : see declaration of 'SV'
...
Lines 4291 and 4292 are:
MY_CXT_INIT
On 22/02/12 16:37, Dave Mitchell wrote:
On Wed, Feb 22, 2012 at 02:50:46PM +, Martin J. Evans wrote:
On 22/02/12 11:09, Dave Mitchell wrote:
It didn't:
It is possible the following is the relevant code after preprocessing:
Hi, it turns out that it's a different section of code
On 22/02/2012 10:45, Tim Bunce wrote:
On Wed, Feb 22, 2012 at 08:55:05AM +, Martin J. Evans wrote:
On 22/02/12 08:22, Martin J. Evans wrote:
The following rt included a patch to apparently fix that issue - or
perhaps it created a new one, or perhaps it did not get in -
https://rt.cpan.org
attributes odbc_batch_size and odbc_disable_array_operations.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 16/02/12 12:46, Tim Bunce wrote:
On Tue, Feb 14, 2012 at 02:06:30PM +, Martin J. Evans wrote:
Should we be updating dbipport.h before next release.
I'll do it we think it should be done. I believe we have 3.19 and 3.20 is
available.
Devel::PPPort is mainly about helping new
in:
if (!PL_dirty !SvTRUE(get_sv(DBI::PERL_ENDING,0))) {
set_err
}
I wasn't sure about the PERL_ENDING bit.
I note that PL_dirty has been replaced in Perl 5.14 but #p5p suggested it is
still ok to use as a macro exists in perl.h.
Martin
--
Martin J. Evans
Easysoft Limited
http
/*introduced in 5.9.5 */
+ HvMROMETA(stash)-cache_gen
#endif
As far as I got during my lunch.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 11/02/2012 00:48, Jan Dubois wrote:
On Fri, 10 Feb 2012, Dave Mitchell wrote:
On Thu, Feb 09, 2012 at 11:10:17PM +0100, demerphq wrote:
Well perls fork() relies on threaded perl so it could very easily be
Dave's patch. Dave do you have access to a win32 build environment?
I'm afraid not.
help debug this?
I do have A windows machine which exhibits the problem.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 10/02/12 10:54, Tim Bunce wrote:
On Thu, Feb 09, 2012 at 09:53:08PM +, Martin J. Evans wrote:
Something between 1.616_901 and 1.616_902 changed which breaks fork() in DBI on
Windows.
Ah, 1.616_901 and 1.616_902! So unrelated to Dave's method cache work.
See if this works
;
}
$::opt_thread = 0;
}
Any reason not to change that to exclude nothread.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 09/02/12 09:15, Martin J. Evans wrote:
I've been testing 1.617 on our development system and have not encountered any
problems as yet. However, I notice a few UNKNOWN smoke reports like the
following one (on mac):
http://www.cpantesters.org/cpan/report/ddd9ac12-5074-11e1-823e-1c11842dab9b
On 09/02/2012 22:12, Tim Bunce wrote:
On Thu, Feb 09, 2012 at 09:53:08PM +, Martin J. Evans wrote:
Something between 1.616_901 and 1.616_902 changed which breaks fork() in DBI on
Windows. The test 16destroy.t fails with a Windows error
This application has requested the Runtime
On 04/02/2012 20:51, Tim Bunce wrote:
On Fri, Feb 03, 2012 at 08:51:10PM +, Martin J. Evans wrote:
You should also be aware that calling odbc_getdiag* will clear DBI's
err, errstr and state so if you want DBI's methods to return
something meaningful you may need to call them first - I'm
-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-O2 -g -DVERSION=\1.34_3\ -DXS_VERSION=\1.34_3\ -fPIC
-I/usr/lib/perl/5.10/CORE -I/usr/include dbdimp.c
It is 2 added calls to DBIh_SET_ERR_CHAR in Driver_xst.h.
Martin
--
Martin J. Evans
On 30/01/12 23:18, Tim Bunce wrote:
On Wed, Jan 25, 2012 at 08:37:57PM +, Martin J. Evans wrote:
I've recently been asked why DBD::ODBC does not tell you which bound
parameter or bound column is in error when an insert/select
specifies a type which the driver cannot convert to e.g., column
On 28/01/2012 10:41, Tim Bunce wrote:
I'd like to make a formal DBI release soon.
DBI-1.616_901 tested well and I've just uploaded DBI-1.616_902.
Any reason I shouldn't upload as DBI-1.617 soon?
Tim.
I'd be happy with that as I'm looking forward to asking people to use
DBI_TRACE=DBD.
I've
I've recently been asked why DBD::ODBC does not tell you which bound
parameter or bound column is in error when an insert/select specifies a
type which the driver cannot convert to e.g., column is varchar(10) and
bind column as an integer and the content cannot be converted to an
integer or
On 21/12/11 13:05, Charles Jardine wrote:
On 12/12/11 20:24, Martin J. Evans wrote:
On 12/12/2011 18:15, Charles Jardine wrote:
On 12/12/11 16:13, Martin J. Evans wrote:
On 09/12/11 18:02, Charles Jardine wrote:
On 09/12/11 14:01, Martin J. Evans wrote:
Hi,
If anyone is around who wrote
On 21/12/11 13:16, Martin J. Evans wrote:
On 21/12/11 13:05, Charles Jardine wrote:
I think I have found the resource drain which causes your
slow-down problem. Buffers implicitly allocated in the cache by
OCIDefineObject() need to be deallocated explicitly by
OCIObjectFree() 'when
On 09/12/11 18:02, Charles Jardine wrote:
On 09/12/11 14:01, Martin J. Evans wrote:
Hi,
If anyone is around who wrote or has worked on the object/collections
support in DBD::Oracle I'd greatly appreciate it if you could take a
quick look at this problem as the code in DBD::Oracle for this has
On 12/12/2011 18:15, Charles Jardine wrote:
On 12/12/11 16:13, Martin J. Evans wrote:
On 09/12/11 18:02, Charles Jardine wrote:
On 09/12/11 14:01, Martin J. Evans wrote:
Hi,
If anyone is around who wrote or has worked on the object/collections
support in DBD::Oracle I'd greatly appreciate
Hi,
I have just uploaded DBD::ODBC 1.34_1 to CPAN. This release adds very
experimental support for a native execute_for_fetch method to DBD::ODBC
which means you can do multiple row inserts/updates/deletes much quicker
than using DBI's default execute_for_fetch (so long as you are using
-execute;
my $r = $s-fetchall_arrayref;
return $r;
}
Thanks
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 09/12/2011 18:02, Charles Jardine wrote:
On 09/12/11 14:01, Martin J. Evans wrote:
Hi,
If anyone is around who wrote or has worked on the object/collections
support in DBD::Oracle I'd greatly appreciate it if you could take a
quick look at this problem as the code in DBD::Oracle
I've been working on support for execute_for_fetch in DBD::ODBC. I've
been looking around for testers and as usual the DBIx::Class users have
come up trumps. However, a question has arisen on irc #dbi which
although I believe I know the answer to it is not specifically mentioned
in the DBI
https://rt.cpan.org/Ticket/Display.html?id=69864
Could someone with the permission to do so move rt 69864 from DBI to DBD:ODBC.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 27/11/2011 13:59, Martin J. Evans wrote:
Sorry, I missed off my proposal for the change to execute_for_fetch
spec - see below:
On 27/11/2011 13:36, Martin J. Evans wrote:
Hi,
I've been trying to implement execute_for_fetch in DBD::ODBC with
some success. However, it is very basic right
Hi,
I've been trying to implement execute_for_fetch in DBD::ODBC with some
success. However, it is very basic right now and only does:
o binds everything as a string in SQLBindParameter and hence relies on
driver/database being able to convert a string to the native column
type. Probably
Sorry, I missed off my proposal for the change to execute_for_fetch spec
- see below:
On 27/11/2011 13:36, Martin J. Evans wrote:
Hi,
I've been trying to implement execute_for_fetch in DBD::ODBC with some
success. However, it is very basic right now and only does:
o binds everything
On 23/11/2011 20:33, Brendan Byrd wrote:
On Wed, Nov 23, 2011 at 9:15 AM, Jens Rehsackrehs...@googlemail.comwrote:
2011/11/23 Brendan Byrdsineswi...@gmail.com:
Well, I'd actually be using schema as a MIB name.
Which is horribly wrong. Tables names like systemGroup are always
full qualified.
J. Evans
Easysoft Limited
http://www.easysoft.com
On 09/11/2011 15:49, H.Merijn Brand wrote:
On Tue, 08 Nov 2011 21:12:13 +, Martin J. Evans
martin.ev...@easysoft.com wrote:
I've just checked in unicode_test.pl to DBI's subversion trunk in /ex dir.
It won't run right now without changing the do_connect sub as you have
to specify how
On 08/11/11 13:16, Tim Bunce wrote:
On Mon, Nov 07, 2011 at 01:37:38PM +, Martin J. Evans wrote:
I didn't think I was going to make LPW but it seems I will now - although it
has cost me big time leaving it until the last minute.
All your beers at LPW are on me!
http://www.martin
On 08/11/2011 13:16, Tim Bunce wrote:
On Mon, Nov 07, 2011 at 01:37:38PM +, Martin J. Evans wrote:
I didn't think I was going to make LPW but it seems I will now - although it
has cost me big time leaving it until the last minute.
All your beers at LPW are on me!
http://www.martin
On 04/11/11 08:39, Martin J. Evans wrote:
On 03/11/11 23:25, David E. Wheeler wrote:
On Oct 7, 2011, at 5:06 PM, David E. Wheeler wrote:
Perhaps we could carve out some time at LPW to sit together and try to
progress this.
That would be awesome you guys!
So gents, do you plan to do
On 05/10/2011 00:06, Jonathan Leffler wrote:
On Tue, Oct 4, 2011 at 15:24, Martin J. Evansmartin.ev...@easysoft.comwrote:
On 04/10/2011 22:38, Tim Bunce wrote:
I've not had time to devote to this thread. Sorry.
I'd be grateful if someone could post a summary of it if/when it
approaches some
J. Evans
Easysoft Limited
http://www.easysoft.com
On 04/11/11 16:39, David E. Wheeler wrote:
On Nov 4, 2011, at 1:39 AM, Martin J. Evans wrote:
Sorry David, I've been snowed under. I will try very hard to publish the
research I found this weekend.
Awesome, thanks.
Did you ever get any data from DBD::SQLite folks?
Yes. I found a bug
I have just uploaded 1.32_2 development release of DBD::ODBC. This
contains one rather nice enhancement for Windows users which adds the
new odbc_driver_complete attribute described as below. Any testing will
be greatly appreciated. The full changes since 1.31 are:
=head2 Changes in DBD::ODBC
On 04/10/2011 22:38, Tim Bunce wrote:
I've not had time to devote to this thread. Sorry.
I'd be grateful if someone could post a summary of it if/when it
approaches some kind of consensus.
Thanks.
Tim.
I don't think there is a kind of consensus right now (although some
useful discussion
to decode data coming back from the
database? and if that is the case do we need some settings in DBI to tell a DBD?
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
David, I forgot to answer your post first and ended up putting most of my
comments in a reply to Greg's posting - sorry, it was a long night last night.
Some further comments below:
On 21/09/11 19:44, David E. Wheeler wrote:
On Sep 10, 2011, at 3:08 AM, Martin J. Evans wrote:
I'm not sure
On 22/09/2011 17:36, David E. Wheeler wrote:
On Sep 22, 2011, at 2:26 AM, Martin J. Evans wrote:
There is more than one way to encode unicode - not everyone uses UTF-8;
although some encodings don't support all of unicode.
Yeah, maybe should be utf8_flag instead.
see below.
unicode
On 10/09/2011 03:52, David E. Wheeler wrote:
DBIers,
tl;dr: I think it's time to add proper Unicode support to the DBI. What do you
think it should look like?
I'm not sure any change is required to DBI to support unicode. As far as
I'm aware unicode already works with DBI if the DBDs do the
On 09/08/11 21:44, Lokkju Brennr wrote:
I'm perfectly happy with spatialite_ - it was my original proposal.
Loki
spatialite_ is reserved as a driver prefix with the driver beingDBD::Spatialite
in DBI's trunk in subversion.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
to get done twice. I think explicitly warning against
my $ar;
eval { $ar = $dbh- selectall_arrayref($SQL); 1} or $dbh-do{$SQL);
would be going too far.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
I have just uploaded DBD::ODBC 1.31 to pause. This is the culmination of
7 development releases and I thought it was time to do an official
release. Due to personal issues I am unlikely to be doing another update
to DBD::ODBC in the near future but if you find issues please report
them on RT
count in NUM_OF_FIELDS.
The only thing I'm not sure about is whether $sth-{NUM_OF_FIELDS} is always
set by $dbh-prepare, or whether some DBMS can't set it until you do
$sth-execute.
Right now, I am unsure of that too.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
Is it ever legal (should be supported) to issue a non select in
selectall_arrayref?
Obviously I think not but I'd like to know what other people think. I'm
getting a few rts from the same person who I believe is moving existing
code from DBD::Sybase to DBD::ODBC. The recent one is that he is
on
bound parameter problems.
* Added new FAQ entry for Firebird
* Removed some unused variables and added some missing function
prototypes
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 16/05/11 20:23, Tim Bunce wrote:
On Fri, May 13, 2011 at 07:07:31PM +0100, Martin J. Evans wrote:
http://www.easysoft.com/dbi.avi
ftp://ftp.easysoft.com/pub/dbi.avi
It is done with codeswarm which you can read about and get at
http://code.google.com/p/codeswarm/. It explains what
On 16/05/11 17:30, Greg Sabino Mullane wrote:
Thanks, Tim, I've adjusted DBD::Pg to throw errors properly.
So have I in DBD::ODBC although I needed to do it in 2 places because of that
bound parameter in Jonathan's example.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
at x.pl line 10.
DBD::ODBC::st execute failed: Unable to fetch information about the error
at x.pl line 10.
It is unable to find why execute failed because the connection is closed.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
http://www.easysoft.com/dbi.avi
ftp://ftp.easysoft.com/pub/dbi.avi
It is done with codeswarm which you can read about and get at
http://code.google.com/p/codeswarm/. It explains what the visualisation is.
I will have to delete these at the end of the weekend.
Martin
I've just uploaded DBD::ODBC 1.30_1 to CPAN.
If you use Windows or a Unicode build of DBD::ODBC on non-Windows
platforms you should really test this release as it contains a change in
behaviour for Unicode. This release also contains a small but perhaps
significant change to the silent
On 09/05/11 22:06, Tim Bunce wrote:
On Mon, May 09, 2011 at 07:42:53PM +0100, Martin J. Evans wrote:
I've recently had an rt posted
(http://rt.cpan.org/Public/Bug/Display.html?id=67994) after a
discussion on stackoverflow
(http://stackoverflow.com/questions/5912082/automatic-character-encoding
On 10/05/2011 09:08, Martin J. Evans wrote:
On 09/05/11 22:06, Tim Bunce wrote:
On Mon, May 09, 2011 at 07:42:53PM +0100, Martin J. Evans wrote:
I've recently had an rt posted
(http://rt.cpan.org/Public/Bug/Display.html?id=67994) after a
discussion on stackoverflow
(http://stackoverflow.com
I've recently had an rt posted
(http://rt.cpan.org/Public/Bug/Display.html?id=67994) after a discussion
on stackoverflow
(http://stackoverflow.com/questions/5912082/automatic-character-encoding-handling-in-perl-dbi-dbdodbc).
In this case the Perl script is binding the columns but the data
something like:
DBD::ODBC::db disconnect warning: Disconnect with transaction in progress -
rolling back
Obviously if you have PrintWarn turned off or are not using warnings it won't
make any difference to you. Anyone have any fundamental objections to this
change.
Martin
--
Martin J. Evans
definitely a mistake if your code could
use multiple DBDs).
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 12/03/2011 10:55, Tim Bunce wrote:
On Fri, Mar 11, 2011 at 10:27:16PM +, Martin J. Evans wrote:
On 11/03/2011 16:53, Tim Bunce wrote:
Time's in very short supply at the moment, but if someone can contribute
tests for these (ideally as patches to existing test scripts) then I'll
fix'em
On 11/03/2011 16:53, Tim Bunce wrote:
Time's in very short supply at the moment, but if someone can contribute
tests for these (ideally as patches to existing test scripts) then I'll
fix'em as soon as I get a moment.
Both are simple:
https://rt.cpan.org/Public/Bug/Display.html?id=66127
some of the examples
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 22/02/2011 17:40, Tim Bunce wrote:
On Mon, Feb 21, 2011 at 05:59:34PM +, Martin J. Evans wrote:
It would appear this problem and possibly other leaks are attracting quite a
lot of attention now. Someone else just posted another cpan rating mentioning
leaks at:
http
.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 13/01/11 18:53, Martin J. Evans wrote:
I briefly looked at the DBD::Pg rt ticket
https://rt.cpan.org/Ticket/Display.html?id=60863 and I'm not sure this is a bug
in DBD::Pg and think it might be in DBI. Since ShowErrorStatement set
On 16/02/11 12:00, John Scoles wrote:
On Wed, Feb 16, 2011 at 5:45 AM, Martin J. Evans
martin.ev...@easysoft.com wrote:
On 11/02/11 18:43, John Scoles wrote:
Here is the latest and greatest DBD::Oracle for your programming pleasure.
You can find the Zip file here
a
href=http
---
t/31lob.t 1 256127 58.33% 9-12
Failed 1/1 test scripts, 0.00% okay. 4/12 subtests failed, 66.67% okay.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
John Scoles
Changes
Added connection attribute 'ora_connect_with_default_signals' that will
localize Perl's $SIG{INT} handler from Brian Phillips and T. Bunce
Fix in execute_array to stop possible endless loop when using a fetch sub by
Martin J. Evans
Adapted Martin J. Evans' ODBC
just did not want to do it that way and would rather work with
what was already present in DBI.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 10/02/11 23:47, Tim Bunce wrote:
On Sun, Feb 06, 2011 at 02:39:09PM +, Martin J. Evans wrote:
On 06/02/2011 13:00, Tim Bunce wrote:
On Sat, Feb 05, 2011 at 01:27:11PM +, Martin J. Evans wrote:
ok, the 3 new trace flags are in and I added macros (slight shame
you cannot use them
On 11/02/11 09:05, H.Merijn Brand wrote:
On Fri, 11 Feb 2011 08:42:21 +, Martin J. Evans
martin.ev...@easysoft.com wrote:
On 10/02/11 22:27, Greg Sabino Mullane wrote:
Trace level is no good to get DBD only tracing since level
1 and 2 is for DBI and anything after that is DBD.
Yes
On 11/02/11 10:36, H.Merijn Brand wrote:
On Fri, 11 Feb 2011 10:14:12 +, Martin J. Evans
martin.ev...@easysoft.com wrote:
On 11/02/11 09:05, H.Merijn Brand wrote:
On Fri, 11 Feb 2011 08:42:21 +, Martin J. Evans
martin.ev...@easysoft.com wrote:
On 10/02/11 22:27, Greg Sabino
.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 06/02/2011 11:16, H.Merijn Brand wrote:
On Sat, 5 Feb 2011 12:29:09 +, Tim Buncetim.bu...@pobox.com
wrote:
On Fri, Feb 04, 2011 at 08:00:13PM +, Martin J. Evans wrote:
Tim,
At the LPW I think I promised to add connection and encoding trace
flags to DBI which add to the already
On 06/02/2011 13:00, Tim Bunce wrote:
On Sat, Feb 05, 2011 at 01:27:11PM +, Martin J. Evans wrote:
ok, the 3 new trace flags are in and I added macros (slight shame
you cannot use them in DBI.pm too but not a great deal).
I think they should be added to the ALIAS list in constant().
Which
On 04/02/2011 20:00, Martin J. Evans wrote:
Tim,
At the LPW I think I promised to add connection and encoding trace
flags to DBI which add to the already existing SQL flag. I never got
around to it and Merijn reminded me today on #dbi. The change is
trivial and once implemented I
On 05/02/2011 12:29, Tim Bunce wrote:
On Fri, Feb 04, 2011 at 08:00:13PM +, Martin J. Evans wrote:
Tim,
At the LPW I think I promised to add connection and encoding trace
flags to DBI which add to the already existing SQL flag. I never got
around to it and Merijn reminded me today on #dbi
On 05/02/2011 12:54, Martin J. Evans wrote:
On 05/02/2011 12:34, Martin J. Evans wrote:
On 05/02/2011 12:29, Tim Bunce wrote:
On Fri, Feb 04, 2011 at 08:00:13PM +, Martin J. Evans wrote:
Tim,
At the LPW I think I promised to add connection and encoding trace
flags to DBI which add
On 03/02/2011 10:01, Tim Bunce wrote:
On Wed, Feb 02, 2011 at 03:52:00PM +, Martin J. Evans wrote:
[...]
So, I think DBI works fine right now (given slight pod change) and
don't want to complicate it or worse, break peoples existing code.
Great! :)
DBD:: Oracle on the other hand does
Tim,
At the LPW I think I promised to add connection and encoding trace flags
to DBI which add to the already existing SQL flag. I never got around to
it and Merijn reminded me today on #dbi. The change is trivial and once
implemented I will replace DBD::ODBC trace flags for connection and
believe this
is permissible
I later noticed:
f) DBD::Oracle was never returning the total rows affected in list context
g) DBI was documenting 2 fields in ArrayTupleStatus for an error put 3 in
On 02/02/11 12:15, Tim Bunce wrote:
On Tue, Feb 01, 2011 at 09:02:26PM +, Martin J. Evans wrote
On 01/02/11 15:44, Tim Bunce wrote:
On Sun, Jan 30, 2011 at 05:46:49PM +, Martin J. Evans wrote:
push @$tuple_status, [ $sth-err, $sth-errstr, $sth-state ];
so I guess the pod should say:
If the execution of a tuple causes an error, then the corresponding
status array element
On 01/02/11 15:50, John Scoles wrote:
On 01/02/2011 10:44 AM, Tim Bunce wrote:
On Sun, Jan 30, 2011 at 05:46:49PM +, Martin J. Evans wrote:
push @$tuple_status, [ $sth-err, $sth-errstr, $sth-state ];
so I guess the pod should say:
If the execution of a tuple causes an error
On 01/02/2011 20:50, Tim Bunce wrote:
On Tue, Feb 01, 2011 at 10:58:14AM -0500, John Scoles wrote:
On 01/02/2011 10:48 AM, Tim Bunce wrote:
On Mon, Jan 31, 2011 at 08:39:40PM +, Martin J. Evans wrote:
I imagine most DBDs [if not all] that implement execute_array
[Just a reminder
On 30/01/2011 17:46, Martin J. Evans wrote:
Hi,
I'm still working on and off with execute_array problems hoping to get
DBI and the spec to match and also investigating if the current
implementation covers all possibilities. I've now written a simple
test to see if it complies
of
affected rows should not sum a load of -1s affected to be -N. So for
DBD::Oracle and array context $rows (in your example) should be -1 as
DBD::Oracle/Oracle does not return the number of affected rows for the
batch or even individually.
Martin
On Sun, Jan 30, 2011 at 12:46 PM, Martin J. Evans
Hi,
I'm still working on and off with execute_array problems hoping to get
DBI and the spec to match and also investigating if the current
implementation covers all possibilities. I've now written a simple test
to see if it complies with the specification (and will include it in
DBD::ODBC)
Firstly, apologies for starting a thread and then being too busy to
follow it up - I really have been very busy but I would like to make
some progress with this.
On 10/01/2011 22:35, Tim Bunce wrote:
On Mon, Jan 03, 2011 at 02:50:21PM +, Martin J. Evans wrote:
On 03/01/2011 13:08, Tim
is
relying on RaiseError so I've changed the DBD::Oracle we use internally to
raise an error.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
101 - 200 of 317 matches
Mail list logo
