John Scoles wrote:
> The way Ping works is different is depending on the version of DBD::Oracle
> you are using. Which version of DBD::Oracle are you using??
>
> cheers
> John Scoles
The patch looked to be against the subversion trunk John.
Martin
> On Thu, Jun 17, 2010 at 2:34 PM, Thomas M. P
Jens Rehsack wrote:
> Hi DBI and DBD developers,
>
> I have some open points for DBD::File I'd like to ask for feedback on them.
>
> The first two are related to the table meta data.
>
> 1) I introduced simple getters and setters for DBD::File table's meta
>data (look for get_file_meta and s
H.Merijn Brand wrote:
> On Mon, 07 Jun 2010 13:51:26 -0400, John Scoles
> wrote:
Others have answered individual items you highlighted, I only have one
point below:
>> H.Merijn Brand wrote:
>>> For my own projects (which includes two DBD's), I have been working on
>>> spell-check issues. I'm not
John Scoles wrote:
> Ok I have patched up a solution I think will work across the board and you
> can find it here
>
> http://svn.perl.org/modules/dbd-oracle/branches/oci_batch
>
> here are the details
>
> ora_oci_batch
>
> For 11g users you may encounter an error while using the execute_array
I have just uploaded the official 1.24 release of DBD::ODBC to CPAN.
Many thanks to everyone who has helped with this whether it was patches
or testing. Here are the changes since 1.23:
=head2 Changes in DBD::ODBC 1.24 May 14, 2010
Minor change in Makefile.PL to only use NO_META if ExtUtils::Ma
ed or fetched
then this impacts similar prepare attributes in DBD::ODBC.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
John Scoles wrote:
>
>
> On Tue, Apr 6, 2010 at 4:51 AM, Martin Evans <mailto:martin.ev...@easysoft.com>> wrote:
>
> I haven'
I recently looked at Test::Database (after I saw it mentioned in the
last QA Hackathon). It does not have specific support for DBD::ODBC
right now but it will work to provide data sources for DBD::ODBC without
change.
One of the big problems I have is finding testers. Most smokers don't
have DBI_D
I've just uploaded the 1.23_5 development release of DBD::ODBC. This
will hopefully be the last release before an official 1.24. Below are
the changes since 1.23. All testing welcome however, once a few smoke
testers have passed this release I am going to move to a full release
fairly quickly as I'
H.Merijn Brand wrote:
> This rocks!
>
> my $dbh = DBI->connect ("dbi:CSV:", undef, undef, {
> RaiseError=> 1,
> PrintError=> 1,
>
> f_dir => ".",
> f_schema => undef,
> f_ext => ".csv/r",
> f_encoding=> "utf8",
> });
>
> Any objections
Jan Dubois wrote:
> On Wed, 14 Apr 2010, Martin J. Evans wrote:
>> As ActiveState do not release development builds (no criticism
>> intended) I am looking at producing a ppm for people to try.
>
> Note that everyone can also just compile the module for themselves
> with ActivePerl:
>
> cpan
Jens Rehsack wrote:
> Hi DBI Developers,
>
> as maintainer of SQL::Statement I try often some easy examples using
> DBD::CSV, because I have a good knowledge what happens behind the
> scenes.
> So I did last days when I played around with threads and
> Log::Log4perl::Appender::DBI. I've seen, than
I haven't seen a reply to this yet but I've been on holiday so might
have missed it:
Scott T. Hildreth wrote:
> On Wed, 2010-03-31 at 12:20 -0500, Scott T. Hildreth wrote:
>> We have run into an issue with array processing in 11g. The developer
>> was using execute_array and his sql statement had
Tim Bunce wrote:
> On Wed, Mar 10, 2010 at 10:25:45AM +0000, Martin Evans wrote:
>
>> 1. the TYPE attribute on a statement is clearly documented as to what it
>> should contain - "The values correspond to the international standards
>> (ANSI X3.135 and ISO/IEC 9075) w
Martin Evans wrote:
> H.Merijn Brand wrote:
>> On Mon, 08 Mar 2010 10:13:02 +0000, Martin Evans
>> wrote:
>>
>> large original chunks snipped ...
>>
>>> H.Merijn Brand wrote:
>>>> I see a big difference in what $sth->{TYPE} returns (and the
H.Merijn Brand wrote:
> On Mon, 08 Mar 2010 10:13:02 +0000, Martin Evans
> wrote:
>
> large original chunks snipped ...
>
>> H.Merijn Brand wrote:
>>> I see a big difference in what $sth->{TYPE} returns (and the name) and
>>> what column_info () - if im
H.Merijn Brand wrote:
> I see a big difference in what $sth->{TYPE} returns (and the name) and
> what column_info () - if implemented - is returning.
I don't think I do with DBD::ODBC (results below).
> From the DBI docs:
>
>Handle attributes:
>
>"TYPE" (array-ref, read-only)
>
>
Tim Bunce wrote:
> On Sun, Mar 07, 2010 at 10:29:29AM -0800, David E. Wheeler wrote:
>> On Mar 7, 2010, at 5:43 AM, Tim Bunce wrote:
>>
Looks good, thanks. Pity you removed the `$dbh->{private_myapp_sql_mode}`
bit, though, as that's required when using C, which
you almost certainly a
John Scoles wrote:
> Horray.
>
> Just one more thing has come up in like the last 15min
>
> can you redo your the make test with the following file
>
> http://svn.perl.org/modules/dbd-oracle/trunk/ocitrace.h
>
> It is a trivial change but just want to make sure it does not break
> anything
>
John Scoles wrote:
> Well here comes the big #5
>
>
> It can be found at the usual place
>
> http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.24-RC5.tar
>
>
> This time round was a patch to fix a patch for some warnings that was
> causing a seg-fault on some 32 bit boxes
>
> Cheers
>
Charles Jardine wrote:
> On 27/01/10 17:38, Martin Evans wrote:
>> Charles Jardine wrote:
>>> On 27/01/10 15:52, Martin Evans wrote:
>>>> Hi,
>>>>
>>>> I was asked to enable ora_verbose and send a trace a few days ago.
>>>>
Charles Jardine wrote:
> On 27/01/10 15:52, Martin Evans wrote:
>> Hi,
>>
>> I was asked to enable ora_verbose and send a trace a few days ago.
>>
>> I'm getting a segfault with DBD::Oracle when ora_verbose or dbd_verbose
>> is set to 15 in the connect
Hi,
I was asked to enable ora_verbose and send a trace a few days ago.
I'm getting a segfault with DBD::Oracle when ora_verbose or dbd_verbose
is set to 15 in the connect method call. The stack trace is:
(gdb) bt
#0 0x080be45c in Perl_sv_vcatpvfn ()
#1 0x080ccd6d in Perl_vnewSVpvf ()
#2 0x081
Just uploaded to CPAN. This is a development release as I've introduced
two significant changes which I'm waiting on feedback for.
=head2 Changes in DBD::ODBC 1.23_2 January 26, 2010
Fixed bug in Makefile.PL which could fail to find unixODBC/iODBC
header files but not report it as a problem. Tha
I've just uploaded a new release of DBIx::Log4perl to CPAN. The changes:
0.18 Mon January 22 2010
Minor speedups in bind_param, bind_param_inout and execute methods.
Thanks to Devel::NYTProf.
Minor speedups in _unseen_sth.
Thanks to Devel::NYTProf.
Fix rt 53755 (fetchrow_array ig
John Scoles wrote:
>
> Well here comes #4
>
>
> It can be found at the usual place
>
> http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.24-RC4.tar
>
>
> This time round I added a little patch from Charles Jardine fro objects
> and some fixes for warnings
>
> I have changed the ora_n
Tim Bunce wrote:
> On Wed, Jan 20, 2010 at 03:24:23PM +0000, Martin Evans wrote:
>>>> but I don't see any call to connect when clone is called.
>>> You don't see a call to DBI->connect, but there is a call to
>>> $drh->connect via the closure.
&
Tim Bunce wrote:
> On Tue, Jan 19, 2010 at 09:04:43PM +, 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
my memory is
not too good these days.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
> Martin Evans wrote:
>> John Scoles wrote:
>>
>>> Thank Charles that is really good stuff
>>>
>>> I have not investigated the
>>>
>>>
> Jardine wrote:
>> On 14/01/10 12:19, Charles Jardine wrote:
>>> On 12/01/10 12:07, John Scoles wrote:
>>>> Ok third time is a Charm
>>>>
>>>> The Third RC of the beer edition of DBD::Oracle 1.24 can be found at
>>>>
>>>>
=
--- t/31lob_extended.t (revision 13722)
+++ t/31lob_extended.t (working copy)
@@ -1,7 +1,7 @@
#!perl -w
##
-## 26exe_array.t
+## 31lob_extended.t
## By Martin Evans, The Pythian Group
## ---
Martin Evans wrote:
> Martin Evans wrote:
>> John Scoles wrote:
>>> Well here it is the long awaited 1.24 Beer version of DBD::ORACLE
>>>
>>> http://sctvguide.ca/images/bd_two-four.jpg
>>>
>>>
>>> You can find the release candidat
Martin Evans wrote:
> John Scoles wrote:
>> Well here it is the long awaited 1.24 Beer version of DBD::ORACLE
>>
>> http://sctvguide.ca/images/bd_two-four.jpg
>>
>>
>> You can find the release candidate here
>>
>> http://svn.perl.org/modules/dbd
Martin Evans wrote:
> John Scoles wrote:
>> Well here it is the long awaited 1.24 Beer version of DBD::ORACLE
>>
>> http://sctvguide.ca/images/bd_two-four.jpg
>>
>>
>> You can find the release candidate here
>>
>> http://svn.perl.org/modules/dbd
oking up csform values
> Fix for rt.cpan.org Ticket #=46763,46998 enhancement -Rowcache size is
> now being properly implemented with row fetch buffer from John Scoles
> Fix for rt.cpan.org Ticket #=46448 enhancement -Errors returned by
> procedures are now unicode strings from Marti
Tim Bunce wrote:
> On Tue, Dec 15, 2009 at 02:53:03PM +0000, Martin Evans wrote:
>> If you are using the latest DBI and Perl 5.10.0 or 5.10.1 and running in
>> taint mode (but have not set DBI's Taint, TainTIn, TaintOut) then use
>> tainted strings in the SQL you i
Martin J. Evans wrote:
> Martin J. Evans wrote:
>> Hi,
>>
>> I've spent some time on this today and I am getting nowhere. Before I
>> redouble my efforts I thought I'd post here just in case anything rings
>> a bell with someone.
>>
>> We are using the latest DBI and DBD::Oracle to get data from an
Tim Bunce wrote:
> On Tue, Dec 08, 2009 at 12:04:25PM +0000, Martin Evans wrote:
>>>> My reading of Perl_sv_2nv() in sv.c is that ifdef NV_PRESERVES_UV
>>>> then SvNOK is not set (but SvNOKp is) if grok_number() returns 0
>>>> into numtype. Th
Martin Evans wrote:
> Tim Bunce wrote:
>> On Thu, Nov 26, 2009 at 07:47:45PM +, Martin J. Evans wrote:
>>> Martin Evans wrote:
>>>> Tim,
>>>>
>>>> I'm not sure if you are bothered by this but there appears to be a small
>>>>
H.Merijn Brand wrote:
> Current checkout:
>
> commit a5a9fc491c2f0316a39af0adb5cd82b39dabafae
> Author: mjevans
> Date: Wed Dec 2 10:08:18 2009 +
>
> Needs SQL types and DBIstcf_XXX
>
>
> git-svn-id: http://svn.perl.org/modules/dbi/tr...@13624
> 50811bd7-b8ce-0310-adc1-d9db26280
Tim Bunce wrote:
>
> Post a diff and I'll review it for you. The code you appended previously
> looks ok.
Attached is a diff for DBD::Oracle based on subversion this morning (the
diffs for oci8.c may be a little difficult to read due to the large
indentation of the surrounding code and there are
Tim Bunce wrote:
> On Thu, Nov 26, 2009 at 07:47:45PM +, Martin J. Evans wrote:
>> Martin Evans wrote:
>>> Tim,
>>>
>>> I'm not sure if you are bothered by this but there appears to be a small
>>> inconsistency between SQL_INTEGER/SQL_NU
Just uploaded 1.23_1 to CPAN. This release contains:
makefile.PL changes:
some formatting changes to output
warn if unixodbc headers are not found that the unixodbc-dev package
is not
installed
use $arext instead of "a"
pattern match for pulling libodbc.* changed
warn if DBI_DSN etc
Thread is getting a bit long so I've snipped a lot of previous code.
Tim Bunce wrote:
> On Mon, Nov 09, 2009 at 05:05:11PM +, Martin Evans wrote:
>> Martin Evans wrote:
>>>>
>
>> There was an omission in my addition to Tim's example as I forgot to
Martin Evans wrote:
> Tim Bunce wrote:
>> On Tue, Oct 27, 2009 at 02:54:43PM +0000, Martin Evans wrote:
>>>> The next question is whether overflowing to an NV should be an error.
>>>> I'm thinking we could adopt these semantics for bind_col types:
>>&
Tim Bunce wrote:
> On Tue, Oct 27, 2009 at 02:54:43PM +0000, Martin Evans wrote:
>>> The next question is whether overflowing to an NV should be an error.
>>> I'm thinking we could adopt these semantics for bind_col types:
>>>
>>> SQL_INTEGER IV
Thanks Tim for the help on this.
Tim Bunce wrote:
> On Mon, Oct 26, 2009 at 05:29:21PM +0000, Martin Evans wrote:
>> What follows is a very rough patch (definitely not finished) which
>> proves you can do what I wanted to do. However, there on no checks on
>> the column bei
Martin J. Evans wrote:
> Hi,
>
> With reference to the rt I created "Support binding of integers so they
> are returned as IVs" at http://rt.cpan.org/Public/Bug/Display.html?id=49818
>
> I am now at the point where being unable to bind columns to results-sets
> in DBD::Oracle with a bind type of
Greg Sabino Mullane wrote:
>
>> I could do what DBD::Pg does here (and have to verify it works) but
>> Oracle integers can be very large - too big to fit in an IV in some
>> cases.
>
> Ah yes, I forgot that Oracle doesn't really have an
Greg Sabino Mullane wrote:
>
>> With reference to the rt I created "Support binding of integers so they
>> are returned as IVs" at http://rt.cpan.org/Public/Bug/Display.html?id=49818
>
> If I'm understanding you correctly, this was recently 'fixed' in DBD::Pg,
> to accomodate JSON::XS as well. Fo
Greg Sabino Mullane wrote:
>
>> With reference to the rt I created "Support binding of integers so they
>> are returned as IVs" at http://rt.cpan.org/Public/Bug/Display.html?id=49818
>
> If I'm understanding you correctly, this was recently 'fixed' in DBD::Pg,
> to accomodate JSON::XS as well. Fo
Thanks for the reply John.
John Scoles wrote:
> Sounds like an easy patch to DBD::Oracle (off the top of my head) I am
> not sure how it would fix into the DBI spec though.
>
> If I am reading the question right you want to be able to tell
> DBI/DBD::Oracle that col X of a return is an int?
Yes
Tim Bunce wrote:
> On Mon, Sep 14, 2009 at 02:12:16AM -0700, hmbr...@cvs.perl.org wrote:
>> Author: hmbrand
>> New Revision: 13334
>>
>> Modified:
>>dbi/trunk/Changes
>>dbi/trunk/DBI.xs
>>dbi/trunk/DBIXS.h
>>dbi/trunk/Driver_xst.h
>>dbi/trunk/Perl.xs
>>dbi/trunk/dbipport.h
>
I have just uploaded DBD::ODBC 1.23 to CPAN. It is a full release of all
the 1.22_x development series releases. The changes since 1.22 are:
=head2 Changes in DBD::ODBC 1.23 September 11, 2009
Only a readme change and version bumped to 1.23. This is a full
release of all the 1.22_x development re
Tim Bunce wrote:
> On Tue, Aug 04, 2009 at 04:13:19PM +0100, Martin Evans wrote:
>> Tim Bunce wrote:
>>> On Tue, Aug 04, 2009 at 01:19:43PM +0100, Martin Evans wrote:
>>>> This is my second attempt to try and get some insight into how to do
>>>> this. The
Tim Bunce wrote:
> On Tue, Aug 04, 2009 at 01:19:43PM +0100, Martin Evans wrote:
>> This is my second attempt to try and get some insight into how to do
>> this. The DBD::ODBC::ping method calls DBI::_new_sth to obtain a new
>> statement handle but DBD::ODBC prevents cre
This is my second attempt to try and get some insight into how to do
this. The DBD::ODBC::ping method calls DBI::_new_sth to obtain a new
statement handle but DBD::ODBC prevents creating a new statement handle
when not connected (you cannot actually get one even if you wanted). The
problem is once
Hi,
I've just received a bug report for a regression in the way ping works
(took over 3 years for someone to notice) in DBD::ODBC. If the
connection handle is not connected when a ping it done you get:
DBD::ODBC::db ping failed: Cannot allocate statement when disconnected
from the database at -e
Hi,
I am sorry to have to admit to being the author of a very very silly bug
in unicode handling in DBD::ODBC. The length of UTF16 encoded data was
stored in an unsigned short and this can overflow. An unfortunate side
effect of this bug can be corruption in your perl application. I only
found thi
H.Merijn Brand wrote:
> On Thu, 4 Jun 2009 11:44:51 -0700 (GMT-07:00), Todd Zervas
> wrote:
>
>> Do you have any thoughts on how DBD::Unify ought to return warnings?
>> Specifically I need to be able to detect "dirty reads" (SQLWARN =
>> -2022). Is the right DBI way to do this to have DBD::Unify
I have uploaded a new development release of DBD::ODBC to CPAN.
This fixes the issue reported in
https://rt.cpan.org/Ticket/Display.html?id=46597 and represents a change
in the behavior for binding parameters as DBD::ODBC was not following
the DBI specification.
If you bind parameters and then al
Tim Bunce wrote:
> On Wed, May 27, 2009 at 04:16:48PM +0100, Martin Evans wrote:
>> Tim Bunce wrote:
>>> How does your DBI driver represent a default column value in the results
>>> returned by the column_info() method?
>>> Specifically, does it distinguish
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Bunce wrote:
> How does your DBI driver represent a default column value in the results
> returned by the column_info() method?
>
> Specifically, does it distinguish between default literal strings and
> default functions/expressions?
>
> Conside
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I released DBD::ODBC 1.20 yesterday. I am happy to accept any make test
results mailed directly to me whether they are success or failure. If
you mail me success results I'll compile a listing of working ODBC drivers.
The changes are listed below the
I have just uploaded DBD::ODBC 1.19 to CPAN where it should start
appearing later today. 1.19 is the result of a lot of hard work in the
previous 4/5 development releases to work around various ODBC driver
bugs. Thank you to everyone one sent me test output and by all means
continue to do so.
If y
Hi,
I have released a new development release of DBD::ODBC 1.18_2 which you
can find on CPAN. For a list of changes see the end of this email.
I would like to make a plea to all DBD::ODBC users to download and at
least run the make test and send the output to me, even if you are not
currentl
I just noticed the thread http://www.perlmonks.org/?node_id=746522 on
perl monks and when I looked at DBD::ODBC, there were 3 issues posted in
the last few days none of which I got an email from. It would appear I
am not the only one.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easys
Raghavachary, Sundeep wrote:
Hello All,
When I am running the DBD-mysql-4.001 with DBI-1.58 on Red Hat 5 EL
(x86_64), it fails at "make test" with the following error code 255.
Can you help me resolving the error?
(In theory transactions could be supported when using a transport that
maintains
John Scoles wrote:
Ok guys and gals how about a little testing with this RC.
This time round I have fixed a bug in the connection function were the
environment handle was lost if one tried to connect with a bad
user/password combination.
You can find it at the same old spot
http://svn.per
[EMAIL PROTECTED] wrote:
Merijn and I have implimented it in DBD::Oracle and DBD::Unify
respectifully. I amd about to review the thread and see if I have to
manke any futher changes to DBD::Oracle.
It think the key is gettin Tim B on board.
I myself have fount it a great help when debugging a
Thanks to all who have responded with clarification. I have implemented
ParamTypes in DBD::ODBC as a hash reference with parameter number as key
and each value is a hash reference with keys of 'TYPE' and values of SQL
type number.
This will be in 1.17_2.
Martin
--
Martin J. Evans
Easysoft Lim
H.Merijn Brand wrote:
On Fri, 10 Oct 2008 16:19:20 +0100, Martin Evans
<[EMAIL PROTECTED]> wrote:
Hi,
The DBI specification for ParamTypes taken from the DBI pod says the
following for ParamTypes:
Returns a reference to a hash containing the type information currently
bo
Hi,
The DBI specification for ParamTypes taken from the DBI pod says the
following for ParamTypes:
Returns a reference to a hash containing the type information currently
bound to placeholders. The keys of the hash are the ’names’ of the
placeholders: either integers starting at 1, or, for
Tim Bunce wrote:
On Sun, Aug 31, 2008 at 11:47:38PM +0100, Martin J. Evans wrote:
Tim Bunce wrote:
On Fri, Aug 29, 2008 at 12:37:48PM +0100, Martin Evans wrote:
Martin Evans wrote:
dbd_st_prepare and dbd_db_login6 both take char* and not the original SV
so how can I tell if the
Martin Evans wrote:
Hi,
Increasingly I am getting asked unicode questions and being presented
with unicode issues that currently don't work in DBD::ODBC. Currenty
DBD::ODBC supports the binding of unicode parameters and the returning
of unicode result-set data.
I would like to chang
Hi,
Increasingly I am getting asked unicode questions and being presented
with unicode issues that currently don't work in DBD::ODBC. Currenty
DBD::ODBC supports the binding of unicode parameters and the returning
of unicode result-set data.
I would like to change DBD::ODBC to support:
a) u
John Scoles wrote:
Ok hot off the press RC3
A few more minor fixed but a last minute patch for ora_lob_chunk_size
function
It can be found in the usual spot
http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.22-RC3.tar
Cheers and thanks for all the help guys
John Scoles
Build
Martin Evans wrote:
Tim Bunce wrote:
On Mon, Jul 28, 2008 at 05:35:14PM -0400, John Scoles wrote:
Gisle Aas wrote:
On Jul 28, 2008, at 18:06, John Scoles wrote:
Ok hot off the press RC2
I have fixed as much as I can of the different compiler warnings
hopefully this will be a little
Tim Bunce wrote:
On Mon, Jul 28, 2008 at 05:35:14PM -0400, John Scoles wrote:
Gisle Aas wrote:
On Jul 28, 2008, at 18:06, John Scoles wrote:
Ok hot off the press RC2
I have fixed as much as I can of the different compiler warnings
hopefully this will be a little better.
You can find the
Tim Bunce wrote:
On Mon, Jul 28, 2008 at 01:13:50PM +0100, Martin Evans wrote:
Hi,
From the DBI::DBD docs in "The dbd_db_login6 method" I read:
=
Here’s how you fetch them; as an example we use hostname attribute,
which can be up to 12 characters long excluding null terminator:
Hi,
From the DBI::DBD docs in "The dbd_db_login6 method" I read:
=
Here’s how you fetch them; as an example we use hostname attribute,
which can be up to 12 characters long excluding null terminator:
SV** svp;
STRLEN len;
char* hostname;
if ( (svp = DBD_ATTRIB_GET_SVP(attr, "drv_hostname",
Martin Evans wrote:
Fails to compile for me with one instant client:
oci8.c: In function 'oci_mode':
oci8.c:242: error: 'OCI_SUPPRESS_NLS_VALIDATION' undeclared (first use
in this function)
oci8.c:242: error: (Each undeclared identifier is reported only once
oci8.c:
it up to standard from Martin Evans
Fix for memory hemorrhage in bind_param_inout_array found by Ricky
Egeland, Fix by John Scoles
Fix for a typo in oracle.xs from Milo van der Leij
Fix for bugs on SPs with Lobs reported by Martin Evans, Fix by J Scoles
Changed the way Ping works rather tha
Tim Bunce wrote:
On Fri, Jul 25, 2008 at 11:00:10AM +0100, Martin Evans wrote:
Thanks for all your hard work on this John. Here are some observations and
results:
o META.yml is missing - you get the following during Makefile.PL processing:
Warning: the following files are missing in your kit
connection part of POB from John Scoles
Fix to test suite to bring it up to standard from Martin Evans
Fix for memory hemorrhage in bind_param_inout_array found by Ricky
Egeland, Fix by John Scoles
Fix for a typo in oracle.xs from Milo van der Leij
Fix for bugs on SPs with Lobs reported by M
H.Merijn Brand wrote:
On Wed, 21 May 2008 09:21:57 +0100, Martin Evans
<[EMAIL PROTECTED]> wrote:
Hi,
I'm hoping someone here may be able to help with an outstanding ticket I
have for DBD::ODBC.
http://rt.cpan.org/Dist/Display.html?Status=Active&Queue=DBD-ODBC
which
Hi,
I'm hoping someone here may be able to help with an outstanding ticket I
have for DBD::ODBC.
http://rt.cpan.org/Dist/Display.html?Status=Active&Queue=DBD-ODBC
which started at http://rt.cpan.org//Ticket/Display.html?id=32789 (for
strawberry perl)
The problem is people using cpan -i on s
David E. Wheeler wrote:
Howdy dbi-devers,
More and more lately, I'm writing database functions in PL/pgSQL (in
PostgreSQL) or SQL (in MySQL and others) to do the heavy lifting of
interacting with database tables. I've been thinking that I'd really
love a DBI method to call these functions wit
Hi,
I have just uploaded DBD::ODBC 1.16 to CPAN. This release contains the
following changes:
=head1 CHANGES
=head2 Changes in DBD::ODBC 1.16 May 13, 2008
=head3 Test Changes
Small change to the last test in 10handler.t to cope with the prepare
failing instead of the execute failing - spott
Tim,
In the thread "problem with DBD::ODBC and placeholders
[SEC=UNCLASSIFIED]" on dbi-users recently you said:
> Drivers that support named placeholders like ":N" where N is an
> integer, could support both forms of binding: bind_param(":1",$v) and
> execute($v)
> It's not dis-allowed. Driver
Tim Bunce wrote:
On Mon, May 12, 2008 at 05:15:34PM +0100, Martin Evans wrote:
Martin Evans wrote:
After seeing the recent posting by Greg Sabino Mullane in subject "Log DBI
query and values with placeholders" I realised there was something else
DBD::ODBC was out of date with - trac
Martin Evans wrote:
After seeing the recent posting by Greg Sabino Mullane in subject "Log
DBI query and values with placeholders" I realised there was something
else DBD::ODBC was out of date with - tracing.
DBD::ODBC does not implement its own trace flags but neither does it
rea
After seeing the recent posting by Greg Sabino Mullane in subject "Log
DBI query and values with placeholders" I realised there was something
else DBD::ODBC was out of date with - tracing.
DBD::ODBC does not implement its own trace flags but neither does it
react to 'SQL' tracing. If I set tra
John Scoles wrote:
Seem this version is mostly problem free? Here is the RC3 for your
enjoyment.
http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.21-RC3.tar
Hopefully the last of the C warnings are gone, Fixed some typos and made
sure the the .yml and manifest files are in the ta
John Scoles wrote:
Martin Evans wrote:
Martin Evans wrote:
John Scoles wrote:
Ok how about try #2
You can find it here
http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.21-RC2.tar
Got rid of the 'OCIXMLTypeCreateFromSrc' waring, seems Oracle has
released this in the A
Martin Evans wrote:
John Scoles wrote:
Ok how about try #2
You can find it here
http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.21-RC2.tar
Got rid of the 'OCIXMLTypeCreateFromSrc' waring, seems Oracle has
released this in the API but not provided a ptototype for it.
Al
John Scoles wrote:
Ok how about try #2
You can find it here
http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.21-RC2.tar
Got rid of the 'OCIXMLTypeCreateFromSrc' waring, seems Oracle has
released this in the API but not provided a ptototype for it.
Also added a patch to provide fast
John Scoles wrote:
The first Release Candidate for DBD::Oracle 1.21 is now ready for your
enjoyment.
You can find it here
http://svn.perl.org/modules/dbd-oracle/trunk/DBD-Oracle-1.21-RC1.tar
Any and all testing would be greatly appreciated, but especially
testing of building against Oracle In
Tim Bunce wrote:
On Wed, Mar 26, 2008 at 03:01:54PM +, Martin Evans wrote:
Hi,
I was attempting to tidy up some code in DBD::ODBC and noticed quite a
number of tests using DBIc_ACTIVE which attempt to signal an error when the
database is not active (not connected). Having never seen
Hi,
I was attempting to tidy up some code in DBD::ODBC and noticed quite a
number of tests using DBIc_ACTIVE which attempt to signal an error when
the database is not active (not connected). Having never seen these
errors I wrote a quick test script and got no errors when calling
prepare, do
Jonathan Leffler wrote:
Good Evening (well, it was evening when I was writing this),
Having just released a new version of DBD::Informix, I've gotten a couple of
bug reports from CPAN Testers about not being able to install it - which is
no vast surprise since those people typically do not have
1 - 100 of 120 matches
Mail list logo
