Robert Boisvert wrote:
I'm working on a project to connect to a SQLExpress database on a Win7x64
computer and running into a problem when I fork to a child process. I know
that it is important to close file handles when forking but I can't seem to
close the ADO handles and the program
Jason Thurston wrote:
Hello,
Does anyone have any ideas where to go from here?
I think perl Makefile.PL is successful but I get an error when
trying the next step make.
The Error I get when trying to make is
/home/foo/DBD-Oracle-1.28/oci8.c:4619: undefined reference to
`_OCIServerRelease'.
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.99.tar.gz
size: 47582 bytes
md5: 05ebf07e4476d3e34468819ab6f6fa08
Changes:
Patch to remove annoying warnings during global destruction,
with tests, from Rafael Kitover.
Implemented more_results().
Added tests (t/26more.t).
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.98.tar.gz
size: 46572 bytes
md5: 92e83467a8b7fe2a831af507893eb728
Changes:
Fixed a 'Missing argument in sprintf' at DBD/ADO/GetInfo.pm line 13.
Patch for supporting cygwin in Makefile.PL from Rafael Kitover.
Added a workaround for
Jeff Picklyk wrote:
I am trying to use the DBD-ADO module with iThreads and keep getting
errors when running the executable that ADO has no driver CLONE()
function so is unsafe threaded. I was hoping to use ADO connection
methods in my application and it does not appear that this is going to
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.97.tar.gz
size: 46460 bytes
md5: cb9815b6a17b47e0d4d5f794242ef8a0
Changes:
Added tests for bind_param_inout() (t/28sp.t).
Patch for supporting bind_param_inout() from Peter Mei.
Steffen
Peter Mei wrote:
Here's a working implementation of bind_param_inout, with explicit support
for the adCmdStoredProc command type. It's been deployed in a production
environment for over half a year, now, without incident, so I'm comfortable
subjecting the public to any remaining bugs.
I've
Markus.Gruber wrote:
- How can i get the insert id which is returned from the database after an
insert-statement?
DBD::ADO doesn't support last_insert_id(), because there is no generic way to
implement it.
For a MS SQL Server specific way, see e.g. @@IDENTITY:
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.96.tar.gz
size: 44664 bytes
md5: 44ab1eec70abfa297d3ceb0d77b5f400
Changes:
Implemented statistics_info().
Added tests (t/45ddst.t).
Fixed bug: Application uses a value of the wrong type for the current
operation, reported by
Rossi EpvTech wrote:
Hello,
I'm using SQLOLEDB to connect to a MSSQL database where I've inserted
some data using the BULK INSERT with the option SET DATEFORMAT DMY.
The SO language installed on the computer where the Sql Server and my
programs runs is English with Italian as regional
[EMAIL PROTECTED] wrote:
Hello all,
Sometimes it is just more sensible to find a workaround rather than a solution.
So, here is an updated script that uses DBI::ADO to create the database, DBI::ODBC
to populate and test it, and DBI::ADO to retrieve the pics via CGI.
Thanks for the
Cosimo Streppone wrote:
Hi all,
I found a strange problem in DBI::type_info().
I don't know much of DBI internals. Only found that sometimes,
the 'type_info_all' structure returned by the driver is
mangled by some shift() that happens in DBI::type_info().
This happens only for DBD::Informix
amonotod wrote:
Hello all,
I'm trying to insert images into an Access database (they're small, and
that's how the app
was built, not my choice), but I'm running into errors. I'm using...
I can reproduce this :-(
[...]
eval {
use Win32::OLE;
Win32::OLE-Option(CP =
jderrick wrote:
Hi Everybody,
DBD-ADO version 2.95 appears to have a problem with the bind_param =
command when using the SQL type constants. The problem does not occur =
with version 2.94. See the dbi-users posting Possible bug in DBD-ADO =
2.94 bind_param from September 24, 2005 for
Mary Anderson wrote:
Hi All,
I have picked up ParseExcel and started to work with it. I am having
a problem with code that essentially looks like this:
for ($iR = 0; ($oWkS-{MaxRows} $iR =$oWkS-{MaxRows}, $iR++){
for ($iC=0; ($oWkS-{MaxCols} $iC =$oWkS-{MaxRows},
Olivier Poulet wrote:
Greetings all,
I have scripts that are running on Win32, with an underlying MDAC/ADO
2.8 RTM version, with MSSQL Server 2000 or 2005 as the database. It is
not possible for us to either update/upgrade MDAC itself, and this
version has a bug in the way it handles the
Luke Bakken wrote:
Hi all,
Attached/included is my hackish attempt to add support for the
adExecuteStream option to ADO.pm. I needed this for retrieving data
from several stored procedures that return XML and it works for my
purposes but I'm not sure if I've integrated it well into ADO.pm
Luke Bakken wrote:
I'll look into execute more() - this is my first foray into DBI
programming at all. Perhaps the stream output should be treated as a
single row, single column return set?
Perhaps. Or, because your data are returned from stored procedures,
it's time to implement
Kumar Talinki wrote:
Hi,
I am using DBI ADO connection to access MS SQL Server. I switched
from ODBC to ADO recently.
ADO connection is returning the date format as mm/dd/yy
hh:mi:ss, where as ODBC connection returns datetime in -mm-dd
hh:mi:ss(24hr)
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-monetdb-0.08.tar.gz
size: 21702 bytes
md5: 9853396da9eb1cddedf3f93f087819db
New PREREQUISITES:
This release and the MonetDB::CLI* 0.02 releases are required
for MonetDB 4.10:
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.95.tar.gz
size: 43510 bytes
md5: 5cf104e54bd2e57c49a3609c9115334e
Changes:
Changed bind_param() to use an optional ado_size attribute.
This is a workaround for the SQLOLEDB bug documented earlier.
Replaced global error variables with
Steffen Goeldner wrote:
I'd like to remark that SQL/CLI has a more general function
GetSessionInfo( ConnectionHandle, InfoType, ... )
general value specification Data TypeCode Information Type
Tim Bunce wrote:
[...]
Why not help save the world and help me add current_schema() to the DBI
and send implementations to the authors of drivers you're using?
I'd like to remark that SQL/CLI has a more general function
GetSessionInfo( ConnectionHandle, InfoType, ... )
general value
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-monetdb-0.07.tar.gz
size: 21696 bytes
md5: ee99c2a93abf5f3fa29263e25ab2f820
New PREREQUISITES:
Instead of MapiLib, this release uses MonetDB::CLI - the MonetDB
Call Level Interface - and one of its implementations.
Steffen
Knut Tvedten wrote:
Using prepared statements doesn't work correctly for driver DBD-ADO
version 2.94 on MS SQL Server 2000 (Provider=sqloledb).
Given CREATE TABLE t1(c1 VARCHAR(255))
The code snippet triggers the error:
...
my $stmt = $dbh-prepare('INSERT INTO t1(c1) VALUES(?)');
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-monetdb-0.06.tar.gz
size: 21780 bytes
md5: e71f47ab668e3f009e47a634fbbd2376
This is the first CPAN release - a snapshot from the CVS repository
at SourceForge:
http://sourceforge.net/projects/monetdb
Alternatively, you can checkout current
Philip Zembrod wrote:
Thank you for the quick reply!
Steffen Goeldner [EMAIL PROTECTED] schrieb am 18.07.05 14:37:00:
Philip Zembrod wrote:
[...]
What I would finally like to do is call a stored proc with an output parameter
through OLE DB. But as yet I can't even call a procedure
Philip Zembrod wrote:
Hello,
I am having trouble calling any stored procedure with a parameter through DBI
and DBD::ADO on a Sybase Adaptive Server Enterprise.
What I would finally like to do is call a stored proc with an output parameter
through OLE DB. But as yet I can't even call a
Rudolf Niehaus wrote:
MAKE Version 5.2 Copyright (c) 1987, 1998 Inprise Corp.
I'd use dmake with Borland.
Steffen
joachim.goerner wrote:
Hi Steffen,
if I load DBD::ADO (with use in my script) is all ok
if I do this not (I think the DBI load DBD::ADO)
the error is writing.
Aah, now I see from your original post: you try to avoid global
destruction (GDP) with an END block - that's o.k.! GDP is the
hell.
joachim.goerner wrote:
[...]
Win32::OLE(0.1702): GetOleObject() Not a Win32::OLE object at
C:/Perl/site/lib/Win32/OLE/Lite.pm line 154 during global destruction.
Oh: 'global destruction'. Can't give much advise here:
http://www.xray.mpe.mpg.de/mailing-lists/dbi/2004-02/msg00085.html
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.94.tar.gz
size: 41994 bytes
md5: 88531f231c006c55328a8f355cb5325d
Changes:
Reworked db/st handle attributes:
- fetching all the data of a SELECT sets Active off
- dropped the RowsInCache attribute (ADO doesn't provide this
Tim Bunce wrote:
At that time I decided to omit this deprecated #define in sqlext.h:
/* Deprecated defines from prior versions of ODBC */
#define SQL_DATABASE_NAME 16/* Use
SQLGetConnectOption/SQL_CURRENT_QUALIFIER */
Attached is a patch - if Tim likes it?
Is there any
Phillip Hellewell wrote:
Hello,
I'm using DBI and DBD:ODBC in my perl script. I'm also using
DBI::Const::GetInfoType. I was trying to get the database name using
$dbh-get_info( $GetInfoType{SQL_DATABASE_NAME} ), and it returned 0,
but $dbh-get_info( 16 ) worked! So I looked in
Stan Banes wrote:
Does anyone have any help here.
I have an application that connects to SQL Server. When my connection
string is thorugh ADO I end up truncating the first two fields but not
the rest of the fields (at least it does not look like I do).
Looks like this problem:
Paul Appleby wrote:
Try measuring the time it takes to connect with SqlPlus by using
You mean DBI? (I already sent the result for sqlplus.)
Time::HiRes with the variables $time1 and $time2 both set to
gettimeofday() and the the length of time set to $time2-$time1, as follows:
Paul Appleby wrote:
I have a simple Perl 5.6 test script that uses DBI and DBD::Oracle to
connect to a local Oracle 9i database
[...]
Why is the connection time so long and how can I shorten it?
[...]
It takes 2.9342188835144 seconds to connect to the database.
How long does it take with
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.93.tar.gz
size: 42606 bytes
md5: c3cad1e4b5576895939423f8130da1bb
Changes:
Implemented do().
Changed $sth-DESTROY to call finish( $sth ) instead of $sth-finish.
The old call caused clearing of errors e.g. in $dbh-do().
Replaced
Tommy Wilson wrote:
I'm using DBD::ADO 2.92 with DBI 1.37 accessing a SQL
Server 2000 database. I've noticed that the driver
doesn't seem to be trapping errors all of the time.
For instance, when I attempt to restore a log that's
out of sequence, I get the following error in SQL
Query
Analyzer:
Sarkissian, Vahe - NC wrote:
I upgraded MDAC to 2.8 before I posted the first message. I got it from
http://msdn.microsoft.com/data. Unless there's a more recent version that
I'm not aware of, I don't think the bug's in the MDAC layer.
FTR: Provider Version = 08.50.1022 (sqloledb.dll) is still
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.92.tar.gz
size: 42406 bytes
md5: b700cbf4ebcd5d9ebe637ad8b7f6b76e
Changes:
Enabled and reimplemented LOB tests (t/27lob.t, t/19misc.t).
Added support for LongReadLen/LongTruncOk.
Minor changes to the STORE() methods.
Moved more
Steffen Goeldner wrote:
Mysterious! Looks like the first execute establishes
a sticky max. length in SQL Server.
Indeed, I can reproduce it with pure ADO (see attached script).
Unfortunately, I don't see a portable workaround for DBD::ADO.
I think it would be best the SQL Server team buys a Shared
Sarkissian, Vahe - NC wrote:
Hi,
I have a workaround for this issue, but the bug appears serious enough that
I wanted to report it to maintainers.
Running a DBD::ADO program against a MS SQL Server 2000 database, if I try
to insert strings using a prepared statement with placeholders, the strings
Hampson, Paul wrote:
I hope this is a bug report, and not me having done something stupid, but
I was told on #perl that it is probably a bug in DBD:ADO.
I'm not subscribed to the mailing, so I'd appreciate a CC for any responses.
Trying to call fetchall_hashref against a statement handle from an
Tim Bunce wrote:
An even more mature, and hopefully even more final, release candidate
of DBD::Oracle 1.16 is available for testing at:
http://homepage.eircom.net/~timbunce/DBD-Oracle-1.16-rc7-20040826.tar.gz
Perl 5.6.1, Win2k, Borland 5.5,
Oracle Client 8.1.7.4.15,
Oracle Server 8.1.7.2.1
Tim Bunce wrote:
An even more mature, and hopefully even more final, release candidate
of DBD::Oracle 1.16 is available for testing at:
http://homepage.eircom.net/~timbunce/DBD-Oracle-1.16-rc7-20040826.tar.gz
Perl 5.6.1, Win2k, Borland 5.5,
Oracle Client 8.1.7.4.15,
Oracle Server 9.2.0.4.0
David N Murray wrote:
Hi all,
I'm having a heck of a time querying a large table. What I'm trying to do
is:
#!/usr/bin/perl -w
use DBI;
use strict;
$|++;
my $dbh = DBI-connect(dbi:ADO:Provider=SQLOLEDB;Integrated Security=SSPI;Data
Source=(local);Initial
amonotod wrote:
From: amonotod [EMAIL PROTECTED]
Date: 2004/08/17 Tue PM 08:25:11 GMT
Use of uninitialized value in subroutine entry at C:/Perl/site/lib/DBI.pm line 595.
DBD::ADO::dr connect warning: at C:/Perl/site/lib/DBI.pm line 595.
Sorry, I didn't mean to forget:
OS: Windows
Jochen Wiedmann wrote:
I'm having a problem utilizing the perl DBI::Proxy to go between a
UNIX (Solaris)
and a Windows SQL server. We started getting an error message
Error while reading socket: Connection reset by peer at
/usr/local/lib/perl5/site_perl/5.6.1/RPC/PlServer/Comm.pm
Tim Bunce wrote:
A mature, and hopefully final, release candidate of DBD::Oracle 1.16
is available for testing at:
http://homepage.eircom.net/~timbunce/DBD-Oracle-1.16-rc6-20040807.tar.gz
Perl 5.6.1, WinNT, Borland 5.5,
Oracle Client 8.1.7.4.15,
Oracle Server 9.2.0.4.0
Tim Bunce wrote:
A mature, and hopefully final, release candidate of DBD::Oracle 1.16
is available for testing at:
http://homepage.eircom.net/~timbunce/DBD-Oracle-1.16-rc6-20040807.tar.gz
Perl 5.6.1, WinNT, Borland 5.5,
Oracle Client 8.1.7.4.15,
Oracle Server 9.2.0.4.0
Tim Bunce wrote:
A mature, and hopefully final, release candidate of DBD::Oracle 1.16
is available for testing at:
http://homepage.eircom.net/~timbunce/DBD-Oracle-1.16-rc6-20040807.tar.gz
Perl 5.6.1, WinNT, Borland 5.5,
Oracle Client 8.1.6.0.0,
Oracle Server 8.1.6.0.0
Using
Tim Bunce wrote:
A mature, and hopefully final, release candidate of DBD::Oracle 1.16
is available for testing at:
http://homepage.eircom.net/~timbunce/DBD-Oracle-1.16-rc6-20040807.tar.gz
Perl 5.6.1, Win2k, Borland 5.5,
Oracle Client 8.1.7.4.15,
Oracle Server 8.1.7.2.1
Using
Olivier Poulet wrote:
Hello to all,
I am running a snippet similar to this against MSSQL 2000, on a Win32
box.
my $sql ='EOFSQL';
SELECT
LOWER(field_one), field_two, UPPER(field_three)
FROM sample_table (NOLOCK)
WHERE
field_one = ?
EOFSQL
my $sth = $dbh-prepare($sql) or die;
my
Joaquin Perez wrote:
Hello,
I have a table with a TEXT field with a size of 16. Theoretically it
could hold up to 2 gigs or something like that.
I've done the following:
$dbh-{LongReadLen} = 2 ** 20 + 8;
$dbh-{LongTruncOk} = 1;
$sth = $dbh-prepare(insert your query here);
Tim Bunce wrote:
1. Specify a fairly short list of the specific SQLSTATE values that
I'd like drivers to support as a minimum.
2. Provide a simple way for drivers to map some of their private
err values into the corresponding SQLSTATE values.
Something like: $drh-{SQLSTATE_map} =
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.90.tar.gz
size: 42569 bytes
md5: 333e1e81fe8e47c85c3c45933608847f
Changes:
Changed default for $dbh-{ado_ti_ver} to 2.
Steffen
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.89.tar.gz
size: 42988 bytes
md5: cde236e5d51ee4097cb0336874851c0f
Changes:
Added an alternative implementation for type_info_all(), which is
enabled if $dbh-{ado_ti_ver} == 2.
!!! The next release of DBD::ADO may default to this new
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.88.tar.gz
size: 42608 bytes
md5: 9c6efb97b312aebbb7709edb13cc7e1d
Changes:
Removed $dbh-{ado_provider_auto_commit_comments} and renamed
$dbh-{ado_provider_support_auto_commit} to $dbh-{ado_txn_capable}.
Changed $dbh-FETCH to handle
Brian Cassidy wrote:
Everything seems to go fine, except at the end of execution I get a strange
error:
[Tue Feb 3 10:56:05 2004] aggregator.pl: Win32::OLE(0.1403): GetOleObject()
Not a Win32::OLE object at D:/Perl/site/lib/Win32/OLE/Lite.pm line 154
during global destruction.
I don't
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.86.tar.gz
size: 43580 bytes
md5: 22b0b9112e439b09e876437d4a095d5b
Changes:
Added support for $sth-{ParamValues}.
Added attribute $h-{ado_max_errors} to avoid time-consuming processing
of huge error collections, suggested by Peter
Hi Peter,
I uploaded a new release of DBD::ADO:
http://search.cpan.org/~sgoeldner/DBD-ADO-2.86/
A new db/st handle attribute
$dbh-{ado_max_errors}
$sth-{ado_max_errors}
limits the number of errors extracted from the errors collection.
(it defaults to 50).
Let me know if it works for
Peter Hircock wrote:
Summary of email sent earlier: Skipping the error step saves 3min in a 5
minute process, where it would take 1 sec if data was returned.
my $rs = $cxn-Execute(...); # Takes 0:54 sec
$_-Description, \n for Win32::OLE::in( $err ); # Takes 3:00
$err-Clear;
Peter Hircock wrote:
I know the ODBC driver is returning SUCCESS_WITH_INFO code 01001.
[Reuters][Open Access][Reuters DB]I41249: Fewer than requested
number of rows retrieved because no more rows found (SQL-01001)
[Reuters][Open Access][Reuters DB]I41255: No rows returned because there
Peter Hircock wrote:
I would like to try that, would I apply the code below to the error
subroutine to limit the number of loops in the for loop. If I understand
this, I could have it leave the for loop once @Err reaches the
MAX_ERRORS.
Better use my test script
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.85.tar.gz
size: 43560 bytes
md5: 13d01bb6c904a150684cf19366487bc7
Changes:
Improved error handling to avoid problems with success/informational
messages, reported by Ed Belisle and Peter Hircock.
These 'success with information'
Peter Hircock wrote:
Steffen Goeldner wrote:
Umm, maybe I need a trace. But I know you are a courageous boy -
thus try this first, please:
use Win32::OLE();
It's still going, I had to run for the weekend.
Memory grew to 300 Meg for 3 min,
released memory ( on 32 ) used,
Printed
Peter Hircock wrote:
Thanks, I had a feeling this was not a quick fix.
The $dbh-errstr is all from the execute()
Umm, maybe I need a trace. But I know you are a courageous boy -
thus try this first, please:
use Win32::OLE();
my $cxn = Win32::OLE-new('ADODB.Connection');
Peter Hircock wrote:
I am having a problem when the query returns no rows, if I get data all
looks good. When I run $sth-execute() on a SELECT that returns no rows,
the OLE-ODBC driver is returning a 01001 Information Code, with the
result. It looks like the ADE driver then enters a
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.84.tar.gz
size: 43265 bytes
md5: ca4b592474bb4533940cadfa90fc799f
Changes:
Reimplemented NULL tests (t/23null.t).
Fixed a DBD::Proxy related bug, reported by Peter Hircock.
The execute() method returned a Win32::OLE::Variant object
Ed Belisle wrote:
1. Yes. All I need to do is detect errors. If there's no error,
excecution continues.
I hope for a discussion at dbi-dev:
http://www.xray.mpe.mpg.de/mailing-lists/dbi/2004-01/msg00204.html
My current workaround is to shell these commands to osql.
Doesn't
local
Peter Hircock wrote:
I get a Storable error on the $sth-execute call when using DBI proxy to
call the DBD::ADO driver. I fell back to DBD-ADO-2.73 an did not get
the same error.
I'm trying to setup a test environment, but have some problems:
Child died: Storable binary image v29.32 more
Peter Hircock wrote:
Yes, can you tell me how to get the previous versions.
E.g.
http://search.cpan.org/~sgoeldner/DBD-ADO-2.77
http://search.cpan.org/~sgoeldner/DBD-ADO-2.76
Steffen
Ed Belisle wrote:
support for CREATE and DROP DATABASE appears to have stopped working
between DBA::ADO versions 2.74 and 2.75. I have tested with MDAC 2.7
SP1 and MDAC 2.8 RTM, and all DBD::ADO Versions from 2.70 through 2.83.
Sorry for the late reply! Indeed, 2.75 reports more errors. I
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.83.tar.gz
size: 43932 bytes
md5: 326867bda2962248b58ce9a372644efb
Changes:
Added notes about Unicode support thanks to Stefan Ram and Jan Dubois.
Rearranged some tests.
Installed ADO-specific method ado_open_schema().
Steffen
Stefan Ram wrote:
The recent message from Jan finally has solved this
mystery and now I can read Unicode data from the
Jet-database. Thanks, Jan!
Some notes of mine regarding Perl and Unicode, including
a small example program showing how to read Unicode from
a Jet-engine database can be
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.82.tar.gz
size: 44212 bytes
md5: d5c48d96a2bb44113d5b2f7001310ea8
Changes:
Replaced duplicated code in DESTROY() with a call to disconnect().
Removed the deprecated Enums() method from DBD::ADO::TypeInfo.
Added t/02ads.t to test
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.81.tar.gz
size: 45171 bytes
md5: e0f78cbdeea4ffe3fb7657131bcbebad
Changes:
Fixed Makefile.PL to work with strict 1.03 (perl 5.8.1.),
reported by Eric Thinnes.
Added ping().
Added tests for ping() to t/02cxn.t.
Removed ping()
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.80.tar.gz
size: 45696 bytes
md5: 558390753464af76f39069e524f5b864
Changes:
Fixed a bug affecting OpenSchema (first row was fetched twice).
Improved the type handling of bind_param().
Steffen
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.79.tar.gz
size: 45270 bytes
md5: f225f35a531d2eeef0ceadb9db3eb62c
Changes:
Added t/51qi.t to test quoted identifiers (and removed similar
tests from t/15func.t).
Added t/07q.t to test quoted values (and removed similar tests
from
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.78.tar.gz
size: 45044 bytes
md5: cf0559199ee51e261d9ccb0d1ca9771a
Changes:
Modified t/09bind.t to use Test::More.
Added data_sources().
Moved some datatype related stuff into DBD::ADO::TypeInfo.
Win32::OLE::Const is no longer
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.77.tar.gz
size: 45221 bytes
md5: d821fa652f996f0b024272de82e1c2dc
Changes:
Added DBD::ADO::Const.
Moved metadata tests into t/4?dd*.t.
Fixed significant bug (missing first row after reexecute) and
added t/12count.t to test row
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.76.tar.gz
size: 45244 bytes
md5: f1f3c6737f32c3f7e222ff9e7b43d502
Changes:
Dropped auto-commit emulation (relying on ADO's default behavior
instead).
Fixed errors like 'Command cannot be issued within a transaction'.
Improved
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.75.tar.gz
size: 44832 bytes
md5: af6bf443e9a096a06133cf3b05efb27f
Changes:
Improved error handling.
Moved get_info() tests from t/15func.t into t/05gi.t and
added diagnosis output.
Steffen
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.74.tar.gz
size: 44414 bytes
md5: 4c34679a9becd2fa67a26e9db536e598
Changes Version 2.74: 2003-10-12
Improved prepare/bind_param/execute for providers which
fail to parse placeholders correctly.
Modified t/05meth.t to
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.73.tar.gz
size: 43659 bytes
md5: f737252a0227963581e19667b6ae4d46
Changes Version 2.73: 2003-10-05
Modified t/17conn.t to avoid an error message on stderr.
Fixed an error in the creation of the $sth-{TYPE} array.
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.72.tar.gz
size: 43463 bytes
md5: d2afb2a7e0eeae9232b3b98eea8ceff6
Changes Version 2.72: 2003-09-03
Moved DBD::ADO::TypeInfo from DBD/ADO.pm to DBD/ADO/TypeInfo.pm.
Fixed number of tests at t/15func.t.
Fixed warning 'Use of
file: $CPAN/authors/id/S/SG/SGOELDNER/DBD-ADO-2.71.tar.gz
size: 42795 bytes
md5: 95e6d64057e2ae7d98411518a5a400a9
Changes Version 2.71: 2003-08-31
New maintainer: Steffen Goeldner [EMAIL PROTECTED].
I want to offer special thanks to Thomas Lowery, who maintained
this module over
Thomas A. Lowery wrote:
DBD::ADO Release 2.7 is available from http://stlowery.net/DBD-ADO-2.7.tar.gz
...
t\09null..You tried to run a test without a plan! Gotta have a plan.
t\11curs..You tried to run a test without a plan! Gotta have a plan.
t\15func..You tried to run a test
Tim Harsch wrote:
Forgive my naivity (or just flawed understanding) but how would one go
about creating a DBD::Access? For instance DBD::Oracle is built on OCI,
does Access have a similar network protocol? I thought that ODBC was
about the only MS supported method of communicating to
Adam vonNieda wrote:
Here's the output from Oracle 7.3.4.. This is on a Solaris 8 box..
dbms_utility.db_version does not appear to exist on Oracle7..
-Adam
[oracle@mastiff /oracle]$ sqlplus sys/password
SQL*Plus: Release 3.3.4.0.1 - Production on Fri Jan 25 17:25:00 2002
Steffen Goeldner wrote:
I'm searching for a reliable way to get the version number
of an Oracle server.
I collected some alternatives:
select * from v$version;
select * from PRODUCT_COMPONENT_VERSION;
set serveroutput on
declare
v varchar2(255);
c varchar2(255);
begin
[EMAIL PROTECTED] wrote:
In Oracle.pm:
$Id: Oracle.pm,v 1.92 2001/08/31 16:23:59 timbo Exp $
$DBD::Oracle::VERSION = 1.12
Perl: v5.6.1 built for sun4-solaris
Oracle: v.8.1.7
I get these four as undef values, which barfs the uninitialized variable
message on line 327.
320 #
Hi,
my test script raises the following error:
Can't set DBI::st=HASH(0x1870f8c)-{NAME}: unrecognised attribute
at C:/opt/perl/site/lib/DBD/ADO.pm line 1144.
The script is very simple:
use DBI();
$\ = \n;
$, = : ;
my $dbh = DBI-connect or die $DBI::errstr;
$dbh-{ RaiseError } =
Hmmm, and maybe not. You can bind it as SQL_CHAR and it should then
preserve the trailing spaces, though I am not sure how oracle will handle it
on it's side.
Ilya
I think it has to do with the external datatype used in OCIBindBy...:
For VARCHAR2, trailing blanks are stripped.
DBD::Oracle currently sets $sth-{TYPE} to 9 (SQL_DATE) for DATE fields.
Seems logical at first but Oracle DATE fields are really date+time fields.
Oracle's own ODBC drivers return 11 (SQL_TIMESTAMP) for DATE fields and
I'm planning to change DBD::Oracle to do likewise.
Tim.
That's only
Tim Bunce wrote:
- av_store(av, i, newSViv(ora2sql_type(imp_sth-fbh[i].dbtype)));
+ av_store(av, i, newSViv(ora2sql_type(imp_sth-fbh+i).dbtype));
Umm, why change from subscript to pointer arithmetic?
ora2sql_type needs more then dbtype, so it's called with imp_fbh_t*
as
Tim Bunce wrote:
Thanks for the info. Do you have any strong objections to DBD::Oracle
replicating the Oracle ODBC results?
I just tested with an older driver.
The Oracle 7.3 ODBC driver returns (via DBD::ODBC!):
TYPE PREC SCALE NAME
- -
2 38 0
98 matches
Mail list logo
