, 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
e. FAILED tests 1-2, 6
>>
>> What was the purpose of the test? It appears to
>> create a temporary table, 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
six -lcrypt -lutil
libc=/lib/libc-2.1.3.so, so=so, useshrplib=false, libperl=libperl.a
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic'
cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'
Characteristics of this binary (from libperl):
Compile-time options: USE_LARGE_FILES
Built under linux
Compiled at Jun 5 2001 10:27:46
@INC:
/usr/lib/perl5/5.6.1/i686-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
atibility. It's
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
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 install
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(?,?)
M
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
statements although there are some ugly
ways around it (that have other side affects) like setting a server-side cursor
such as a dynamic cursor.
See perldoc DBD::ODBC and search for odbc_SQL_ROWSET_SIZE but I'd redesign the
code to use one statement at a time if I were you.
Martin
--
This is useful, however, if you
want the error handling and asynchronous messages (see
the err_handler) below. See t/20SQLServer.t for an
example of this.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 11-Sep-2003 [EMAIL PROTECTED] wrote:
> Hi,
>
&g
On 11-Sep-2003 [EMAIL PROTECTED] wrote:
>
> Hi,
>
> I'm not trying to connect to the 2 db's at the same time, so I'm not sure
> what you mean.
Appologies, I clicked reply on the wrong message. My reply was for Jenda
Krynicky.
Sorry about that.
--
Martin J. Evans
Easysoft Ltd, UK
Development
This is useful, however, if you
want the error handling and asynchronous messages (see
the err_handler) below. See t/20SQLServer.t for an
example of this.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 11-Sep-2003 Jenda Krynicky wrote:
> Is there a way
On 11-Sep-2003 Jenda Krynicky wrote:
> From: "Martin J. Evans" <[EMAIL PROTECTED]>
>> I haven't tried it in a long time (other than running make test) but
>> from perldoc DBD::ODBC:
>>
>>odbc_async_exec
>>Allow asynchronou
I could be wrong but I didn't think you could use parameters to change the SQL
which you appear to be doing by using ? where a column name is expected.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 15-Oct-2003 Gary Stainburn wrote:
> Hi folks,
>
> can anyone see
$dbh);
under SYNOPSIS and:
@ary = DBI->data_sources($driver);
@ary = DBI->data_sources($driver, \%attr);
under "data_sources"
The above code works fine with DBI 1.13 and DBD::ODBC 0.28.
Any ideas?
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
BD::ODBC::dr (DBI::dr=HASH(0x8242454)~INNER)
! <- DESTROY= (not implemented) during global destruction
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 12-Nov-2003 Tim Bunce wrote:
> On Wed, Nov 12, 2003 at 09:28:54AM -, Martin J. Evans wrote:
>> Hi,
>>
>> I
DBI:ODBC:join
-- DBI::END
-> disconnect_all for DBD::ODBC::dr (DBI::dr=HASH(0x81e6a78)~0x823a300)
<- disconnect_all= '' at DBI.pm line 642
-> DESTROY for DBD::ODBC::dr (DBI::dr=HASH(0x823a300)~INNER)
<- DESTROY= (not implemented) during global destruction
M
On 12-Nov-2003 Tim Bunce wrote:
> On Wed, Nov 12, 2003 at 01:48:14PM -0000, Martin J. Evans wrote:
>> Tim,
>>
>> Whilst I'm trying to narrow this issue down to just DBI or DBD::ODBC here is
>> a
>> level 2 trace (against the now installed DBD::ODBC 1.06):
Mitchell,
Can you generate an ODBC trace to locate exactly how the invalid cursor state
occurs. You can do this from the ODBC Administrator trace tab.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 12-Dec-2003 Mitchell, Louise M wrote:
> All,
>
> I've posted bits o
I answered this email sent to me then it was resent to dbi-users.
Here is what I said:
-FW: <[EMAIL PROTECTED]>-
Date: Tue, 30 Dec 2003 18:00:43 - (GMT)
From: "Martin J. Evans" <[EMAIL PROTECTED]>
To: "Mitchell, Louise M" <[EMAIL PROTECTED]>
gth = 511
Text Len Ptr = 0xb596
[ODBC][14265][SQLError.c][461]
Exit:[SQL_NO_DATA]
[ODBC][14265][SQLError.c][504]
Entry:
Environment = 0x8246b98
SQLState =
Is this the problem you are seeing:
There is a mistake in the Makefile.PL. Edit the Makefile.PL and search
for "NOOP" to find the line:
@$(NOOP)
Replace the spaces in front of "@$(NOOP)" with a character.
Now rerun perl Makefile.PL.
Martin
--
Martin J. Evans
Easysoft
27;d guess so since after the change I highlighted DBD::ODBC 1.06 builds fine
for me. What happens when you untar DBD::ODBC and make the single change I
refer to?
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
> -Original Message-
> From: Martin J. Evans [mailto:[EMAIL PROTEC
I think that should be 'dbi:ODBC:DSN=MSSQL' or 'dbi:ODBC:MSSQL' but the error
message would have helped.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 20-Jan-2004 Herbold, John W. wrote:
> I am trying to hit a MS SQL server using DBI:ODBC from an win2k
Do not open the attachment it is a virus (MyDoom).
I go loads of them from the start of this week.
There is loads on the net explaining this new virus.
The email address is spoofed.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 29-Jan-2004 Hardy Merrill wrote:
> Just check
gt;fetchrow_array) {
print join(",", @row);
}
$dbh->disconnect;
$ ./x.pl mHowell->
1,The quick brown fox jumps over the lazy dog
Have you tried doing this from odbctest or the query analyser?
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
should be calling SQLDriverConnect when the
connection string contains a driver=. Perhaps this is because you are using
"driver=" instead of "DRIVER=" (the ODBC spec is a bit hazy on this but always
uses "DRIVER".
If you get no further with mdbtools and still need to access a mdb from UNIX
let me know as I can suggest other commercial ways.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
t but I thought it comes out of the box
with a driver manager which is in /usr/lib and /usr/include. I think all you
need to do is specify ODBCHOME as /usr.
The Makefile.PL will examine ODBCHOME looking for various possibilities of ODBC
driver managers and drivers to link with. Your ODBCHOME needs to match one of
these - usually libodbc.so, libiodbc.so, sql.h, sqlext.h etc.
BTW, isn't 10.2.4 a pre-release of MAC OS X?
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
t;prepare($query);
> $sth->execute();
I believe there are examples in the sqlserver test file in the subdir t of
DBD::ODBC distribution. Those examples work for me using DBD::ODBC.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
DBI does not need unixODBC.
If you want to use the DBD::ODBC driver under DBI you'll need an ODBC driver or
(more likely) an ODBC driver manager (like unixODBC) and an ODBC driver.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 07-Sep-2004 Christian Stalp wrote:
> Hello ther
//www.unixodbc.org where there are examples of odbc.ini and
odbcinst.inio files.
> Can you give me an example how to connect to the database via the UnixODBC?
> $dbh = DBI->connect ( ? )
May be if I knew what ODBC driver you are using
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
try turning on ODBC tracing in the driver manager, repeat and post the
trace (although it may be quite large in which case I'll take a look at it if
you send it to me). To turn on ODBC tracing, go to the ODBC administrator and
look on the trace tab.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
De
::ODBC
there is a column and it fails on a call to SQLDescribeCol (because
SQLNumResultCols lied and there is no result-set).
Your only choice is to take the prints out.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 19-Oct-2004 Moosmann, James wrote:
> Enclosed is the full trace
ch everyone will be using.
I wait to be proved wrong but I still don't think DBD::ODBC is doing anything
wrong here.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 19-Oct-2004 Moosmann, James wrote:
> Ooops.. here is the link:
>
> http://support.microsoft.com/defau
rces or set the ODBCINI env var to point to your odbc.ini file.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 09-Nov-2004 Dan Scott wrote:
> On Mon, 8 Nov 2004 15:17:34 +0100, Miroslav Lauš <[EMAIL PROTECTED]> wrote:
>> Hi all!
>>
>> I'm using DBD::D
Look at odbc_more_results in DBD::ODBC and the same in the test cases in the
subdir called t when DBD::ODBC is unpacked.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 01-Dec-2004 Marc TRAVAILLE wrote:
> Good evenning,
>
> I create a calculate Select on SQL Server:
>
&
y potential values if it is
multi-choice) and a list of optional attributes. The application can request
the values (or just one value at a time) from the user then feed them back to
SQLBrowseConnect - it repeats this until all the compulsory attributes are
supplied.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
][ODBC SQL Server
Driver]String data, right truncation (SQL-01004)(DBD: st_fetch/SQLFetch (long
truncated DBI attribute LongTruncOk not set and/or LongReadLen too small)
err=-1) at ./tut2_9.pl line 24.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
libodbc.* in /usr/local/stow/iodbc-3.52.1/lib?
If there is and you are sure 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:
> Wel
you are using 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
>
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. Ev
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
27;%s', '%s'\n", dbname, uid, pwd);
and it is not appearing in your log.
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
0 || strstr(upper_dsn, "PWD=") != 0);
}
If the above returns NULL the following code would cause what you are
seeing:
if (strlen(dbname) > SQL_MAX_DSN_LENGTH || dsnHasDriverOrDSN(dbname) &&
!dsnHasUIDorPWD(dbname))
d:
rc = SQLGetFunctions(imp_dbh->hdbc, SQL_API_SQLMORERESULTS,
&supported);
if (ODBC_TRACE_LEVEL(imp_dbh) >= 3)
PerlIO_printf(DBIc_LOGPIO(imp_dbh), " SQLGetFunctions -
SQL_MoreResults supported: %d\n",
supported);
if (SQL_ok(rc)) {
imp_dbh->odbc_sqlmoreresults_supported = supported ? 1 : 0;
} else {
Just means you can use odbc_more_results method.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
_results.
Martin
--
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.
>
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=686&product=2002
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 31-Mar-2005 Moreno, Javier wrote:
> Kevin,
>
> I tried removing the
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
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-O
en DBD::ODBC is not installed.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 17-May-2005 Stephen More wrote:
>> You are probably getting this because you have mixed Perl, unixODBC, MySQL
>> where some were built with -pthread and some were not.
>
> Can this be pro
phtml?ID=664&product=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:
&g
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
eem to be complaining about my 'DSN
> not found or my driver not specified'. Can someone tell me if the
> following syntax is ok or if any other major no-no's jump out at you?
>
> 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
TECTED]
Sent: Thursday, June 02, 2005 5:00 AM
To: dbi-users@perl.org
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 "ODB
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
Devel
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 statem
/
I think 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 Acce
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
WSET_SIZE. However,
you must be very careful to make sure the cursor is closed properly when using
these methods or the MS SQL Server driver can hang on a later statement.
For portability, I never use multiple active statements. I always reorganise my
SQL or if that can't be done open another connection.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
th a scale of 4
(since that's what sql 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=?&qu
4
LEN = 5
Devel::Peek Dump output looks nothing like what I expected.
Also, do I have to use {ora_csform => SQLCS_NCHAR}? Does not seem to work in
either case if I don't.
And one final thing. If I change $x containing the UTF-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
Easysoft Ltd, UK
Development
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 t
code data? Is DBD::Oracle working
correctly 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 t
T changing directory, run you Perl script
perl /path_to_my_script/xxx.pl
4. send me the resulting esoobclient.log_ which will appear in /tmp (where
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 i
tin
-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
qlType=%s, ColDef=%d\n",
@@ -2747,7 +2748,7 @@
}
cbColDef = phs->biggestparam;
}
-
+
if (!SvOK(phs->sv)) {
/* if is_inout, shouldn't we null terminate the buffer and send
* it, instead?? */
@@ -2766,6 +2767,7 @@
} else {
rgbValue = NUL
it any worse than 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 test
g into problems. Ask them why they need to set
odbc_default_bind_type (perhaps it is to make DBD::ODBC work like it
used to before SQLDescribeParam and they don't want to change their code to
bring it up to date).
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
> Brian
>
>
ynchronous messages (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 strin
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 th
Michael,
I think with InstantClient OCIEnvCreate fails if you set ORACLE_HOME. You need
to make sure libclntsh.so is on your dynamic linker search path
(LD_LIBRARY_PATH) and do /not/ set ORACLE_HOME.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 19-Aug-2005 [EMAIL PROTECTED] wrote
artin
--
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
tried 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.
>
> How
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 d
;\0' && isdigit(*cp)) {
+ cp++;
+ ibScale++;
+ }
+ }
+ }
+break;
case SQL_TIMESTAMP:
case SQL_TYPE_TIMESTAMP:
Why not just pass your parameters in as strings and l
(I refer to above) as well 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: Ma
On 06/09/2013 17:52, Martin J. Evans wrote:
On 06/09/13 09:18, Martin J. Evans wrote:
On 05/09/13 20:28, Mike Grau wrote:
Hello,
I am completely new at this, but I am trying to read a BLOB in chunks
via ODBC in Oracle 11g using DBD::ODBC-1.43, unixODBC-2.3.1 and
oracle-instantclient11.2-odbc
xed RT 84450 - Database Handle Attribute Fetch broken. Thanks to
Stephen Oberholtzer for finding and supplying patch.
Fixed problem with attributes on bind_col not being sticky. You'll
probably only see this if you are using fetchall_arrayref with a
slice and setting TYPE or attributes in
heck
http://cpansearch.perl.org/src/PYTHIAN/DBD-Oracle-1.66/README.help.txt
Martin
--
Martin J. Evans
Wetherby, UK
On 18/09/13 09:58, Michael Seaton wrote:
Hi there,
I and a colleague have been trying to install Koha (an integrated
library system written in Perl) onto a server. While we've been mostly
successful in installing Koha, we keep getting the following message
whenever we try to log in:
Can't use a
On 18/09/13 10:26, Martin J. Evans wrote:
On 18/09/13 09:58, Michael Seaton wrote:
Hi there,
I and a colleague have been trying to install Koha (an integrated
library system written in Perl) onto a server. While we've been mostly
successful in installing Koha, we keep getting the foll
identify your problem. If this file ends up empty, try again with:
DBI_TRACE=15=x.log perl myprogram.pl
Martin
--
Martin J. Evans
Wetherby, UK
32 bit or 64 bit SQLLEN
run odbcinst -j on your machine to see how unixODBC was built.
d) include a unixODBC trace - which by the way, the one you sent me was
not a unixodbc trace - it was the start of the DBI trace.
Martin
--
Martin J. Evans
Wetherby, UK
*From:* Martin J. Evans
*To:* Nage
driver is broken
b) it was built with SQLLEN 4 bytes instead of 8 bytes
Neither of (a) or (b) DBD::ODBC can do anything about and both would
require you contacting vertica to get a fixed ODBC driver.
Martin
--
Martin J. Evans
Wetherby, UK
*From:* Martin J. Evans
*To:* Nagendra Singh
*Cc:*
Notice the "incompatible change".
I vaguely recollect this change. Does 1.618 work for you? Can you find
the code which called fetchall_arrayref and show us it as I don't use Koha.
Martin
--
Martin J. Evans
Wetherby, UK
I've just uploaded DBD::ODBC 1.45 to the CPAN. As always I'd draw your
attention to a few small changes in behaviour. The changes since 1.43 are
listed below but I need to warn you about an upcoming change first.
WARNING - PLEASE READ:
=
The next development cycle of DBD::ODBC will contain
the github repository (which you'll find at
https://github.com/pythian/DBD-Oracle).
As You can see I have defined *sub* *plsql_errarray* which select
error info from database and returns them in array reference much more
convinient for later use; *plsql_errstr* only converts that array into
a single string. Of course one should provide at least two additional
parameters to new plsql_errstr function.
Martin
--
Martin J. Evans
Wetherby, UK
e...: 4
SQLLEN Size: 4
SQLSETPOSIROW Size.: 2
2. add to the top of the odbcinst.ini file:
[ODBC]
Trace=yes
TraceFile=/tmp/unixodbc.log
3. now run your basic script and send me /tmp/unixodbc.log
As to whether DBD::ODBC should issue an error if the driver says there is a
problem and then won't tell us what it is - that is another issue I prepared to
debate.
Martin--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On 06/11/13 12:36, Jan Holčapek wrote:
Hi Martin,
3. now run your basic script and send me /tmp/unixodbc.log
attached is the log file you've requested. Please let me know your
findings, thanks!
--Jan
Hi Jan,
Your log shows:
[ODBC][7270][1383740710.126962][SQLExecDirect.c][240]
On 06/11/13 14:36, Jan Holčapek wrote:
Hi Martin,
On Wed, Nov 6, 2013 at 3:05 PM, Martin J. Evans wrote:
I believe this is a bug in your ODBC driver.
I kind of expected that. I'll file a bugreport to Vertica Support.
good, that was part of what I was hoping to achieve when I did
ot support schemas - even
for a simply ping (which uses SQLTables)). Now we call
SQLCATALOG_NAME and SQLSCHEMA_USAGE on connect to ascertain support
which modifies SQLTables call.
[MISCELLANEOUS]
Added test 45_unicode_varchar.t for MS SQL Server only so far.
Martin
--
Martin J. Evans
Wetherby, UK
On 17/11/2013 08:32, Meir Guttman wrote:
Dear Martin
-Original Message-
From: Martin J. Evans [mailto:boh...@ntlworld.com]
Sent: שבת 16 נובמבר 2013 12:34
To: dbi-users@perl.org; DBI Developers Mailing List; dbi-annou...@perl.org
Subject: DBD::ODBC 1.46_1 released - You REALLY need to
On 20/11/13 09:39, Michiel Beijen wrote:
Hi,
I ran into this issue with DBD::ODBC;
I read Martin asked about feedback on the 1.46_1 devel release. I
tested my code against both versions 1.43 and 1.46_1 an the results
are the same.
Thanks for this. It has raised questions that needed answering
MS Access (which does not support schemas - even
for a simply ping (which uses SQLTables)). Now we call
SQLCATALOG_NAME and SQLSCHEMA_USAGE on connect to ascertain support
which modifies SQLTables call.
[MISCELLANEOUS]
Added test 45_unicode_varchar.t for MS SQL Server only so far.
_arrayref, DBI returned:@retarr contains: markb ro
Installed versions
====
perl -MDBD::mysql -le 'print $DBD::mysql::VERSION;'
4.013
perl -MDBI -le 'print $DBI::VERSION;'
1.609
Martin
--
Martin J. Evans
Wetherby, UK
BC (if you know different and can point me
at it I'll take a look). The traditional way around this is to use
temporary tables.
Martin
--
Martin J. Evans
Wetherby, UK
Just so everyone knows, I pointed hhferreira here in the following thread on
perl monks:
https://perlmonks.org/?node_id=1071794
Martin
On 24/01/14 10:29, hhferreira wrote:
Hi Guys,
Hope you can provide us some enlightenment!
We have the following code which basically calls an oracle procedu
On 24/01/14 10:29, hhferreira wrote:
Hi Guys,
Hope you can provide us some enlightenment!
We have the following code which basically calls an oracle procedure passing as
inputs 6 bind arrays (converted in ORA_VARCHAR2_TABLE elements) and one string:
/my $sth = $self->prepare( q{/
/
On 24/01/14 12:26, hhferreira wrote:
Hi,
We have already tried using ora_maxarray_numentries and other similar
attributes unsuccessfully.
Martin found that immediately before the error the following message is written:
{{ execute callback CODE(0xb832be8) being invoked
However we have done a
On Fri, Jan 24, 2014 at 1:28 PM, Martin J. Evans mailto:martin.ev...@easysoft.com>> wrote:
On 24/01/14 12:26, hhferreira wrote:
Hi,
We have already tried using ora_maxarray_numentries and other similar
attributes unsuccessfully.
Martin found that immediately be
1 - 100 of 590 matches
Mail list logo
