, insert some values and retrieve them again to make
sure they are correctly inserted.
I am in the process of getting verbose output for the test but if someone knows
the reason for the upgrade advice I'd love to know.
Thanks.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
they are correctly inserted.
I am in the process of getting verbose output for the test
but if someone knows the reason for the upgrade advice I'd
love to know.
I wish I remembered more and documented it...
Regards,
Jeff
--
Martin J. Evans
Easysoft Ltd, UK
Development
-linux
/usr/lib/perl5/5.6.1
/usr/lib/perl5/site_perl/5.6.1/i686-linux
/usr/lib/perl5/site_perl/5.6.1
/usr/lib/perl5/site_perl/5.005
/usr/lib/perl5/site_perl
.
Thanks,
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
probably not as useful now, but it allowed get_info
and get_type_info to return correct/updated
information that ODBC 2.x didn't permit/provide.
but as far as I can see if you set it to 2 it will call SQLSetEnvAttr for ODBC
2.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Jeff,
one new issue with 1.06.
o line 297 of the generated Makefile contains
@$(NOOP)
but those are spaces leading up to it instead of a tab. The line at fault is
actually Makefile.PL line 427.
o the problem I reported (email subject line) still exists after I fixed above
and
I could be wrong but I think it is the ':' in the time that is causing the
problem. The DBD thinks the ':' is a parameter.
Insert the dates/times with placeholders instead and I think you'll find it
works. e.g. INSERT INTO tblCar (date_now,time_now) VALUES(?,?)
Martin
--
Martin J. Evans
Edit Makefile.PL and look for the lines like this:
config :: $(changes_pm)
@$(NOOP)
You'll find the chrs in front of @$(NOOP) are spaces and they should be a tab.
Fix and rerun perl on the Makefile.PL.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 08-Jul-2003 Anil Menon wrote
) at ./tut2_9.pl line 24.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
you've got iodbc you may need to delete the
unixodbc line above from the Makefile and rerun perl Makefile.PL.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 20-Dec-2004 [EMAIL PROTECTED] wrote:
Well I am having some trouble getting DBD::ODBC up and running and so here
I am. I
the unixODBC you have
just built.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 04-Jan-2005 Honza Pazdziora wrote:
Hello,
I have succesfully installed
freetds-0.62.3-1.1.fc3.rf from Dag Wieers's rpm repository
unixODBC-2.2.9-42
unixODBC-devel-2.2.9-42
Just in case it helps anyone else I had a similar problem. I installed Oracle
9.2.0.1.0 with the Administrator install and did not have an oci.h. I went back
and did a custom install to find Oracle Call Interface was not installed by
default.
Thanks Jeff for the pointer.
Martin
--
Martin J
The DontDlClose was a suggestion to stop the seg faulting on exit.
When I said you can use DSN=emanuel-sbart;UID=*;PWD=*; I did of course mean to
say you need to keep the 'dbi:ODBC' on the front. i.e.
'dbi:ODBC:DSN=emanuel-sbart;UID=*;PWD=*;'
Martin
--
Martin J. Evans
Easysoft Ltd, UK
On 22-Feb-2005 Walter Obermiller wrote:
Martin,
Martin J. Evans wrote:
The DontDlClose was a suggestion to stop the seg faulting on exit.
When I said you can use DSN=emanuel-sbart;UID=*;PWD=*; I did of course mean
to
say you need to keep the 'dbi:ODBC' on the front. i.e
.
BTW I only pointed out you can used dbi:ODBC:DSN=x;UID=y;PWD=z; because
you were mentioning the dsn not found and no default data source message.
Does the plain old DBI-connect('dbi:ODBC:fred', 'user', 'pass') work?
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 22-Feb-2005 Walter
) SQL_MAX_DSN_LENGTH || dsnHasDriverOrDSN(dbname)
!dsnHasUIDorPWD(dbname)) {
sprintf(dbname_local, %s;UID=%s;PWD=%s;, dbname, uid, pwd);
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
--sql.log--
[ODBC][25635
method.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 01-Mar-2005 David N Murray wrote:
Hi all,
Since we seem to be on the subject of Stored Procedures, I thought
I'd throw my problem out there, since I can't figure out what I'm
doing wrong.
The SP builds a temp table, updates the source
msdn.microsoft.com
which lists all the possibilities.
This URL in our FAQ lists many of them:
http://www.easysoft.com/products//faq_answer.phtml?ID=686product=2002
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 31-Mar-2005 Moreno, Javier wrote:
Kevin,
I tried removing the user and the pwd
Have you got sqltypes.h in /home/harbinger/tle/6_0/odbcHPUX/include?
Is this the full C compiler or the one that comes with HP-UX for rebuilding the
kernel?
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 07-Apr-2005 Cory Cox wrote:
I am trying to install the DBD-ODBC version 1.13
threaded or not (on some Linuxes/glibcs).
Try adding DontDLClose = 1 to the driver entry in odbcinst.ini.
Try rebuilding unixODBC and MySQL with -pthread to make them all the same.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 16-May-2005 Stephen More wrote:
I have compiled DBD-ODBC-1.13
(or wherever your Perl is)
run -MDBI -e 'my $dbh = DBI-connect(dbi:ODBC:xxx, user, pass);'
When it crashes enter bt for a back trace.
Of course to do this you'd need to install DBI and DBD::ODBC or look at the
make test to see how to run when DBD::ODBC is not installed.
Martin
--
Martin J
=2002
You need to try PERL_DL_NONLAZY=1. If the problem goes away then see the rest
of the faq above for how to make sure unixODBC is built without the RTLD_GROUP
flag to dlopen.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 19-May-2005 Stephen More wrote:
Here is the info from my bt
You can fix it for yourself by removing the RTLD_GROUP from unixODBC and
rebuilding it. See the FAQ I pointed you at.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 19-May-2005 Stephen More wrote:
The interesting thing is I can't see unixODBC - I thought you were using
unixODBC
?
export
DBI_DSN='dbi:ODBC:host=something.something.something;port=1521;dbname=na
me'
I'm very new to all this and would appreciate as much detailed help as
possible. Thanks for any info
--
Martin J. Evans
Easysoft Ltd, UK
Development
Subject: Re: [dbi] DSN's
For the DSN-less connections, see http://www.connectionstrings.com --
great resource.
Dan
On 6/2/05, Martin J. Evans [EMAIL PROTECTED] wrote:
Sharon,
The string after ODBC: is usually a DSN name as in:
DBI-connect(dbi:ODBC:mydsn,...)
or
DBI-connect(dbi:ODBC:DSN
will get
hangs).
BTW, the example in the pod should be $dbh-{odbc_SQL_ROWSET_SIZE} = 2 not
$dbh-{SQL_ROWSET_SIZE} = 2.
I would seriously suggest you try and avoid multiple active statements - there
is nearly always a SQL or some other way.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
Terence,
I could be wrong but from what little I remember from TDS I think
that unless you enable a server-side cursor, once you start retrieving
data from the server you have no choice but to keep reading it until
it is exhausted - this is why SQL Server ODBC driver only supports
1 active
there is an equivalent in DBD::ODBC.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 23-Jun-2005 Ron Savage wrote:
Hi Folks
Sorry if you've seen this, but I did not receive a copy.
(This is under WinXP, with a DSN pointing to an MS Access db).
Is there an ODBC function call
Daniel,
On 22-Jun-2005 Daniel Kasak wrote:
Martin J. Evans wrote:
As far as I am aware this is a limitation of the TDS protocol used and
your example code will not work unless you force a server-side cursor (see
DBD::ODBC pod and look for odbc_SQL_ROWSET_SIZE but I warn you that you
really
On 27-Jun-2005 Daniel Kasak wrote:
Jeff Urlwin wrote:
Please read DBD::ODBC pod. Specifically the section on the odbc_cursortype.
Jeff
I just added odbc_cursortype= DBI::SQL_CURSOR_DYNAMIC to our
connection string, and that didn't help things at all.
Martin J. Evans ( see other
server says money has).
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 12-Jul-2005 Daniel Kasak wrote:
Hi all.
I'm using the process:
my $sth = $dbh-prepare ( update xxx set a=?, b=?, c=? where d=? );
$sth-execute( $a, $b, $c, $d );
to update data in a SQL Server database
-8 data to insert and run
$sth-execute again it inserts the original data again and not the changed $x.
I've not confirmed this yet with other drivers, but I am /fairly/ sure with
DBD::ODBC you don't have to call bind_param again if the bound data is changed.
Thanks.
Martin
--
Martin J. Evans
fields and reading it via
Oracle's ODBC driver in MS Access - where it looks fine. But, retrieving it in
Perl does not display the same results.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 18-Jul-2005 Martin J. Evans wrote:
Hi,
Wondered if anyone can tell me if I've misunderstood
or should I have done something else?
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 19-Jul-2005 Martin J. Evans wrote:
Hi,
I have some further information on my problem. The insertion of UTF-8 data
into
nchar seems to work like it does for nvarchar2; it appears
directory, run you Perl script
perl /path_to_my_script/xxx.pl
4. send me the resulting esoobclient.log_PID which will appear in /tmp (where
PID is the process ID).
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 25-Jul-2005 Brian Becker wrote:
I am trying to bind an undef
.
Martin
-Original Message-
From: Martin J. Evans [mailto:[EMAIL PROTECTED]
Sent: Monday, July 25, 2005 12:59 PM
To: dbi-users@perl.org
Subject: RE: MsSQL DBD::ODBC IsNull and undef
Brian,
I presume by Easysoft you mean Easysoft ODBC-ODBC Bridge?
If so, can you run your test script
)) {
/* if is_inout, shouldn't we null terminate the buffer and send
* it, instead?? */
@@ -2766,6 +2767,7 @@
} else {
rgbValue = NULL;
phs-cbValue = SQL_NULL_DATA;
+ cbColDef = phs-cbColDef;
}
}
else {
Martin
--
Martin J. Evans
Easysoft Ltd, UK
before and should
make your case work BUT it is a very quick hack. I'll try and
find time to put a better patch together for Jeff.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 26-Jul-2005 Brian Becker wrote:
Was this supposed to happen? A large # of tests now fail...
t/07bind
(see
the err_handler) below. See t/20SQLServer.t for an
example of this.
setting this (from DBD::ODBC pod).
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 01-Aug-2005 Mitchell, Adam R wrote:
I'm having a problem where the error string from a raiserror (inside
In what way is it not working - I /think/ these versions work for me and I only
see a require for Perl 5.4 (DBD::ODBC) and 5.6 (DBI).
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 12-Aug-2005 [EMAIL PROTECTED] wrote:
Guys,
Could you please let me know if there is a DBD::ODBC
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 14-Sep-2005 Jeff Zucker wrote:
I've created a module that marries DBI with AJAX to support LiveGrids -
dynamically updateable portions of web pages that work like google
maps. As you scroll through the grid, the contents are buffered
in SQL::Abstract::Limit and it generates
SQL that does not return the correct rows (as quoted in my previous email)
unless order is specified.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 16-Sep-2005 Martin J. Evans wrote:
Jeff,
Nice one.
However, it does not quite work with my DBD
On 16-Sep-2005 Jeff Zucker wrote:
Martin J. Evans wrote:
Jeff,
The $order parameter is required if $rows is specified.
Ah, yes, of course, thanks for spotting that. To confirm, does it scroll
correctly when you do specify an order (i.e. by clicking on a column
heading to toggle
pass your parameters in as strings and leave the
parameter type off the bind call.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
SAMPLE CODE
=
#!/usr/local/bin/perl -Tw
use strict;
use DBI;
my $dsn = dbi:ODBC:dsn_IRB;
our $dbh = DBI-connect($dsn, '', '', {AutoCommit
and I think that
didn't end up anywhere because after presenting the problem and a fix being
provided, odbc_default_bind_type was introduced.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
Lee Anne
-Original Message-
From: Martin J. Evans [mailto:[EMAIL PROTECTED]
Sent
,
bind_type_guessing);
I fixed be moving the declarations.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
oops, forgot to say this was the DBD::mysql developers release 3.0002_3.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 02-Nov-2005 Martin J. Evans wrote:
Just in case this helps anyone else.
I've just tried DBD::mysql for the first time and it failed to compile with
gcc
2.95.3
. loses an error
Any ideas?
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
- as in:
perl -e 'my @a=(); print $#a;' outputs -1 for an empty list, not 0 for a list
containing an undef.
It does not seem to matter what the driver is - I tried dbi::ODBC too.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
groups that made this clear.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
David Nicol wrote:
On 12/6/05, Martin J. Evans [EMAIL PROTECTED] wrote:
On 06-Dec-2005 Andy Hassall wrote:
If this is the case, then it seems that Google Groups should either make
their version of the group read-only (this would seem to be the most
sensible option since it's really a mailing
will not fail and will NOT see the table does exist. A
SQLPrepare/SQLExecute does however return the connection to mysql server has
been lost.
I don't like cross posting so I'll be mentioning this separately on the
myodbc list.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
);
It also fails if you only have 1 data source but that can be fixed by changing
the comparison:
cmp_ok($#data_sources, '=', 0, data sources test);
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
with modules that provided
backwards compatibility with the old perl4 APIs (ie Oraperl).
Setting $sth-{Compat} = 1 will make DBIc_COMPAT(imp_sth) true.
So that gives you a pure-perl workaround.
Tim.
p.s. I've no idea why it's used in DBD::mysql in this way.
==
Martin
--
Martin J. Evans
can explain what
my_get_fbav and my_setup_fbav were written to acheive.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 15-Feb-2006 Tim Bunce wrote:
On Tue, Feb 14, 2006 at 06:16:30PM -, Martin J. Evans wrote:
Regarding my posting with a problem using DBI 1.50
into dbdimp.c got changed to 51.
A trace of the 20SqlServer test might help.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 02-Mar-2006 Jonathan Gillespie wrote:
Hello,
I'm having problems getting DBD::ODBC 1.13 to work with perl 5.8.8
I'm running CentOS 4.2 with the latest
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 03-Mar-2006 Ron Savage wrote:
Hi Folks
When I call primary_key_info(undef, undef, 'table name in lower case') I get
back an undefined sth and hence can't get primary key info.
Should I expect this to work? I can't see anything
As Will writes, I use transactions within DBD::mysql with MySQL 5 but
ONLY if using innodb tables. i.e. you need to add the innodb to the
create table defn.
Typically, I ignore Autocommit and do a $dbh-begin_work then
a $dbh-commit - works fine so long as you remember transaction
timeout which
for DBD::ODBC::st
(DBI::st=HASH(0x8ac55d8)~0x8ac5638 1 SCALAR(0x89a2d64) 50 4)
-Original Message-
From: Martin J. Evans [mailto:[EMAIL PROTECTED]
Sent: Friday, March 03, 2006 10:03 AM
To: dbi-users@perl.org
Subject: RE: [dbi] DBD::ODBC with Perl 5.8.8
Jonathan,
The test that fails works
(phs-sv, 50)
but
SvLEN(phs-sv) returns 52!
and DBD::ODBC does not expect this.
Certainly does not happen in 5.8.7. I'm out of my depth for the moment on this
now. If any one has any ideas on this I'd appreciate them.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 06-Mar
Sorry,
I meant:
svGrow(phs-sv, 50 + 1)
SvLEN(phs-sv) returns 52!
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 07-Mar-2006 Martin J. Evans wrote:
Hi again. I've now had a chance to take a quick look at this. I can reproduce
with DBI 1.50 and DBD::ODBC 1.13
it stood out -
should that be *sizeof(WCHAR).
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 15-Mar-2006 Alexander Foken wrote:
Hello DBI-users,
I've written a first patch for DBD::ODBC to support Unicode. The patch
was developed to make a custom project management
Tom Mornini wrote:
You need to turn AutoCommit off with:
my $dbh = DBI-connect('dbi:Pg:dbname=test', 'postgres', '...',
{ PrintError = 1, RaiseError = 0,
AutoCommit = 0 });
You should not have to turn autocommit off with begin_work:
From the docs:
Enable
be Postgres library version related.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 26-Mar-2006 John Siracusa wrote:
On 3/26/06 4:00 AM, Martin J. Evans wrote:
Tom Mornini wrote:
You need to turn AutoCommit off with:
my $dbh = DBI-connect('dbi:Pg:dbname=test', 'postgres
get dbh-{Statement}: unrecognised attribute error in test
caused by change to perl internals in 5.8.0
and a diff of 1.36/1.37 seems to have added the strEQ test for Statement
(above). Is this a similar case perhaps?
Thanks.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
Tim,
Thanks for the confirmation.
I added:
|| (*key=='U' strEQ(key, Username))
and my problem has gone away.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 27-Mar-2006 Tim Bunce wrote:
On Mon, Mar 27, 2006 at 02:04:30PM +0100, Martin J. Evans wrote:
Hi,
I
;
mysql_stmt_close(stmt);
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
Could the list maintainer please remove this person - every time I post I get
one of these:
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
-FW: [EMAIL PROTECTED]-
Date: 27 Mar 2006 19:39:39 +0300
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Easily
];
prepare: select b from mytest where a = ?
!!! no execute here
Or, perhaps I'm doing something wrong.
Can anyone tell me if I should be seeing the execute when $dbh-select*** is
called? I think I should.
Thanks
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
The issue I am seeing is not quite as general as I made it sound. For
selectrow_hashref I see prepare/execute/fetch/fetchrow_hashref (as I expect) but
for selectrow_arrayref and selectrow_array I only see prepare.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 29-Mar-2006
are correct or is it that DBI does not check for
its existence?
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
subclassed DBI to know this?
b) is there an easy way to identify which other methods this could apply to
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 29-Mar-2006 Tim Bunce wrote:
On Wed, Mar 29, 2006 at 11:54:32AM +0100, Martin J. Evans wrote:
The issue I am seeing is not quite
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
need as much info as possible at the time of the problem
and I need it as light weight as I can make it because slowing it
down sometimes hides the problem.
Martin
Tim Bunce wrote:
On Wed, Mar 29, 2006 at 04:49:32PM +0100, Martin J. Evans wrote:
Tim,
Thanks, I do keep forgetting about Driver.xst
Tim Bunce wrote:
On Wed, Mar 29, 2006 at 09:58:16AM -0800, Mark Hedges wrote:
On Wed, 29 Mar 2006, Tim Bunce wrote:
On Wed, Mar 29, 2006 at 10:53:56AM +0200, Peter J. Holzer wrote:
On 2006-01-31 01:24:18 +0100, Patrick Galbraith wrote:
I apologise for what might seem somewhat of a bit of
Tim Bunce wrote:
On Wed, Mar 29, 2006 at 09:02:43PM +0100, Martin J. Evans wrote:
Thanks Tim. I'm now hopefully looking in the right places.
Not seeing execute on a selectrow_array threw me initially
but it is an example of the problems I'm seeing.
I'm having a few problems accessing things
Patch against dbd::mysql 3.0002_4 which demonstrates that if you prepare
a statement and execute multiple times then as soon as one execute fails
all subsequent executes fail. This obviously effects execute_array in
particular as all the tuple_status values from the failed execute
onwards show an
the ArrayTupleStatus which is optional since 1.38.
Thanks again for pointing out ParamArrays.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
ParamArrays.patch
Description: ParamArrays.patch
to install something else in Perl or make other
changes.
You need Test::More -
http://search.cpan.org/~mschwern/Test-Simple-0.62/lib/Test/More.pm
and by the looks of the script, you will later need the oracle and mysql dbds
which you'll also find on cpan.
Martin
--
Martin J. Evans
Easysoft Ltd
Jeff to comment.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
Peter Loo wrote:
Hi,
I am trying to pass an array reference to $sth-execute and I am
getting the following error:
DBD::ODBC::st execute failed: called with 38 bind variables when 0 are
needed at /usr/local/apps/common/devl/bin/GlobalRoutines.pm line 42.
The code I am using is as follows:
Hi,
I could really do with a little assistance form the dbd::mysql
maintainers or authors please.
I am investigating the issue I reported here with execute_array or all
executes failing after one execute fails.
i.e.
create table test (a int primary key)
prepare(insert into test values(?)
Siegfried Heintze wrote:
Is there an example somewhere of accessing an MSAccess database from a SuSE
or RedHat machine via perl DBI?
Here is what I am presently using with ActiveState Perl to access the
MSAccess database on windows:
my $dbh = DBI-connect(dbi:ODBC:driver={Microsoft Access
::ODBC and DBD::mysql - both were OK (but my DBD::mysql is
massively patched).
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 06-Apr-2006 Karl Berry wrote:
Greetings,
I'm wondering about how to retrieve the error from bad sql passed to
selectall_arrayref
not
using AutoCommit should explicitly call commit or
rollback before calling disconnect.
I was a bit surprised to see the comment on Oracle automatically committing. I
believe there is a way to stop this happening at the oci level.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http
Martin J. Evans wrote:
On 07-Apr-2006 Jie Zhang wrote:
Hi,
If I initiate a connection using autocommit=0 in DBI and I don't do
a explicit connection-commit(), should transactions automatically
commit after I do an explicit connection-disconnect()? I was
expecting an automatica rollback
changed
how we used OCI. I'll have to look this up after the weekend.
This would suggest it is how DBD:oracle uses OCI.
If you don't hear anything early next week mail me personally to
remind me to look it up.
Martin
thanks,
Jie
Martin J. Evans wrote:
Jie Zhang wrote:
Tom and Martin
the following patch for a test case to dbi-users list:
http://www.nntp.perl.org/group/perl.dbi.users/28909
Original posting and followups:
http://www.nntp.perl.org/group/perl.dbi.users/28896
http://www.nntp.perl.org/group/perl.dbi.users/28908
Martin
Martin J. Evans wrote:
Hi,
I could really do
of the
logging does not come out. You may also want to look a the notes in the pod as
you will need to make a small fix to DBI to get Username and ParamArrays out.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 12-Apr-2006 Tim Bunce wrote:
- Forwarded message from Tomas Karlsson
application is running all the time and when it goes wrong I need as much
info as possible (especially whilst we are developing it). It is not practical
to use DBI's trace - it is too slow, uses too much disk space and is too
difficult to find what I need.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http
?
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
or ODBCINSTINI environment variables have you? If not then the only
thing I can suggest is you send an strace (Linux) or truss (Solaris) of the
isql run - don't bother mailing it to the list - it will be too big.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 20-Apr-2006 Simon
Ben,
Two testa failed because Sybase does not support data type -3 - that is
not a problem.
One test failed because you have not yet defined any data sources in the
odbc.ini file - not a problem.
You can ignore these.
Martin
Ben Ostrowsky wrote:
Hi folks --
I've got Easysoft's latest
.
However, 07005 says:
The statement associated with the StatementHandle did not return a result set.
There were no columns to describe.
so that would suggest you SQL is no a result-set generating statement
i.e. not a select statement.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
Patrick Galbraith wrote:
Martin J. Evans wrote:
Martin,
Thanks much! This is dbdimp.c, right?
Yes
I will add this tomorrow (not
working today),
and I'm stricly not working tomorrow - bank holiday - but it is likely
I'll find time to do something.
and test it out. If everything is a go
Patrick Galbraith wrote:
Martin J. Evans wrote:
Martin,
Sure, I'll be glad to put in the code. If you can come up with tests,
that's one thing we need. Whatever you like, and whatever works for you.
I'll always give you due credit.
Slightly confused as I think I provided tests
On 30-Apr-2006 Patrick Galbraith wrote:
Martin J. Evans wrote:
Martin,
Sure, I'll be glad to put in the code. If you can come up with tests,
that's one thing we need. Whatever you like, and whatever works for you.
I'll always give you due credit.
I also would like to know how
Paul DuBois wrote:
On 5/6/06 11:54, Patrick Galbraith [EMAIL PROTECTED] wrote:
Dear DBD::mysql users,
DBD::mysql version 3.0003 (stable, production) and 3.0003_1 (dev) have
been released!
Version 3.0003 is the production version with server-side prepare
statements turned off by default, and
will result
in NULL (or whatever the default is), but shouldn't it return a string
'NULL'?
No - it returns undef.
Any help will be appreciated.
Thanks
Mike
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
==by 0x80613AD: perl_run (in /usr/bin/perl)
==5361==by 0x805E866: main (in /usr/bin/perl)
==5361==
finish is throwing stuff away that the mysql client still has the address of.
I think the problem would be worse if the example was using bound columns.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
1 - 100 of 540 matches
Mail list logo
