.
STH
--
E-Mail: Scott T. Hildreth [EMAIL PROTECTED]
Date: 25-Jan-02
Time: 12:59:39
--
() is currently a fairly
slowly moving target and has a way to go yet before it's ready for
drivers to use.
..and the code that is in current DBI has changed quite a bit.
--
E-Mail: Scott T. Hildreth [EMAIL PROTECTED]
Date: 05-Feb-02
Time: 08:36:46
--
David,
I have had similar problems with FreeBSD, Linux, and OSF.
http://www.perlmonks.org/index.pl?node_id=323847
what ended up doing is renaming the site_perl/5.6.1 directory to
a temp name, while I upgraded to 5.8.*. Once everything was
installed under 5.8.*, moved
All test pass, FreeBSD 4.9 perl 5.8.1
On Fri, 2004-03-12 at 07:21, Tim Bunce wrote:
On Fri, Mar 12, 2004 at 12:01:55AM +, Tim Bunce wrote:
On Thu, Mar 11, 2004 at 04:26:40PM +, Tim Bunce wrote:
A release candidate is available for testing at:
And another:
And another:
http://lists.perl.org/showlist.cgi?name=dbi-dev
On Fri, 2004-03-12 at 11:05, Lance Prais wrote:
How do I get removed from this list?
I am so tired of seeing 30- messages in my inbox from Tim Bruce..
Please help
-Original Message-
From: Scott T. Hildreth [mailto:[EMAIL
This should be on the dbi-users list. Are you sure all of the
environment variables are set? Can you show the code? The
ORA-12154 is TNS error,
12154, 0, TNS:could not resolve service name
// *Cause: The service name specified is not defined correctly in the
// TNSNAMES.ORA file.
//
Tim,
Are you still maintaining DBD::Proxy? Have you had a request for
supporting named parameters?
STH
On Thu, 2004-10-21 at 16:55, Scott T. Hildreth wrote:
I was going bring this up myself. I had this problem the other day.
To get it working I changed
this is a known bug. I copied the table to a 9i instance and the ran
the code below, and it worked fine. So it seems to be related to 10g.
Thu, 2005-10-20 at 14:07 -0500, Scott T. Hildreth wrote:
I am going to investigate more, but I thought I would post the question
to see if anyone has run
up. dbish is not up to the greatness of DBI
I suggest documenting in DBI that there is no more dbish
--
Scott T. Hildreth [EMAIL PROTECTED]
the implementation been made more
efficient?
Thanks,
Shree
--
Scott T. Hildreth [EMAIL PROTECTED]
) and removes dependency on Class::Accessor.
I'd be grateful for any testing, and especially for feedback on DBD::Gofer
(previously mentioned as DBD::Forward, but DBD::Gofer is a much better name
:)
Enjoy!
Tim.
--
Scott T. Hildreth [EMAIL PROTECTED]
On Fri, 2007-02-02 at 11:50 +, Tim Bunce wrote:
FreeBSD 6.1
This is perl, v5.8.8 built for i386-freebsd
** All tests pass.
--
Scott T. Hildreth [EMAIL PROTECTED]
size: 121582 bytes
md5: 157f817d26a52aaaff61ce38f7043b95
--
Scott T. Hildreth [EMAIL PROTECTED]
On Wed, 2007-03-07 at 16:58 -0600, Scott T. Hildreth wrote:
mysql Ver 12.21 Distrib 4.0.15, for suse-linux (i686)
... So my client is not = to SQL_STATE_VERSION, but dbdimp.c
still has do_error accepting a sqlstate param,
void do_error(SV* h, int rc, const char* what, const char
On Thu, 2007-03-08 at 12:23 -0600, Scott T. Hildreth wrote:
On Wed, 2007-03-07 at 16:58 -0600, Scott T. Hildreth wrote:
mysql Ver 12.21 Distrib 4.0.15, for suse-linux (i686)
... So my client is not = to SQL_STATE_VERSION, but dbdimp.c
still has do_error accepting a sqlstate param
of the failures are due to the older client being used.
Would you like a patch of what I changed?
Thanks.
--
Scott T. Hildreth [EMAIL PROTECTED]
!
The files:
file: $CPAN/authors/id/C/CA/CAPTTOFU/DBD-mysql-4.004.tar.gz
size: 122247 bytes
md5: ba89b04b003dec320c893f2553a98ede
Also:
http://search.cpan.org/~capttofu/DBD-mysql-4.004/
Kind regards,
Patrick Galbraith
--
Scott T. Hildreth [EMAIL PROTECTED]
is to run the Proxy server in debug mode and figure out
why numFields
is not filled in. I was hoping someone might know what is going on before I do
that.
Thanks
On Thu, 2007-01-18 at 15:37 -0600, Scott T. Hildreth wrote:
###
Perl
On Wed, 2007-03-28 at 15:59 -0500, Scott T. Hildreth wrote:
On Wed, 2007-03-28 at 21:26 +0100, Tim Bunce wrote:
On Wed, Mar 28, 2007 at 01:54:51PM -0500, Scott T. Hildreth wrote:
I should also mention that this is a $dbh-do( an insert statement).
A quick look at DBI::ProxyServer, shows
process enable transactions for DBD::Gofer?
Probably still stateless, thought I would ask.
If so please start a new thread and I'll give a brain dump...
--
Scott T. Hildreth [EMAIL PROTECTED]
,
Patrick
Scott T. Hildreth wrote:
Pat,
The #ifdef's still need to be removed in the calls below.
Thanks.
dbdimp.c: In function `mysql_st_fetch':
dbdimp.c:3429: error: too few arguments to function `mysql_dr_error'
dbdimp.c:3593: error: too few arguments to function
On Wed, 2007-03-28 at 21:26 +0100, Tim Bunce wrote:
On Wed, Mar 28, 2007 at 01:54:51PM -0500, Scott T. Hildreth wrote:
I should also mention that this is a $dbh-do( an insert statement).
A quick look at DBI::ProxyServer, shows that the NUMFIELDS indicates
a select, therefore in this case
.
On Wed, 2007-03-28 at 13:01 -0500, Scott T. Hildreth wrote:
Feel free to send it to me before release, we will have the old client
on that server until we upgrade it. Which will be awhile.
On Tue, 2007-03-27 at 22:18 -0400, Patrick Galbraith wrote:
Scott,
Thanks! I need to somehow
On Wed, 2007-04-11 at 09:59 -0500, Scott T. Hildreth wrote:
I had to add this to dbdimp.c, mysql_warning_count() is not implemented
before 4.1,
#if MYSQL_VERSION_ID = SQL_STATE_VERSION
imp_sth-warning_count = mysql_warning_count(imp_dbh-mysql);
#else
imp_sth-warning_count = 0;
#endif
On Mon, 2007-04-23 at 12:34 -0500, Scott T. Hildreth wrote:
I can confirm this,
http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/aa1a09e3ac0aa54f/6d96262964f376aa?lnk=stq=Not+permitted+for+method+connected+of+class+DBI%3A%3AProxyServer%3A%3Adb+rnum=1#6d96262964f376aa
. At first I thought
it was a problem with 64bit Perl client connecting to 32bit Perl Server,
but downgrading to DBI-1.53 on the 64bit server fixes the Proxy problem.
I will try DBI-1.55rc1 and report back.
--
Scott T. Hildreth [EMAIL PROTECTED]
On Mon, 2007-04-23 at 16:41 -0500, Scott T. Hildreth wrote:
On Mon, 2007-04-23 at 21:23 +0100, Tim Bunce wrote:
On Mon, Apr 23, 2007 at 12:38:36PM -0500, Scott T. Hildreth wrote:
On Mon, 2007-04-23 at 12:34 -0500, Scott T. Hildreth wrote:
I can confirm this,
http
On Wed, 2007-04-25 at 22:34 +0100, Tim Bunce wrote:
On Wed, Apr 25, 2007 at 02:45:47PM -0500, Scott T. Hildreth wrote:
On Wed, 2007-03-28 at 21:26 +0100, Tim Bunce wrote:
On Wed, Mar 28, 2007 at 01:54:51PM -0500, Scott T. Hildreth wrote:
I should also mention that this is a $dbh-do
not ok 9 - match char
# Failed test 'match char'
# at t/80ora_charset.t line 83.
# got: '?'
# expected: ' '
/\
||
a char I can't print, looks like a degree symbol :-)
not ok 10 - match char
# Failed test 'match char'
# at
I am not sure how to describe this, my co-worker will run his process and get a
core dump
(I pasted the back trace below) and then run the process again with no core
dumps. Sometimes
it will core dump several times in a row and then the next run it finishes
fine. I ran the process
with
On Thu, 2008-02-14 at 10:03 -0600, Scott T. Hildreth wrote:
not ok 9 - match char
# Failed test 'match char'
# at t/80ora_charset.t line 83.
# got: '?'
# expected: ' '
/\
||
a char I can't print, looks like a degree
On Wed, 2008-03-05 at 17:39 -0600, Scott T. Hildreth wrote:
On Thu, 2008-02-14 at 10:03 -0600, Scott T. Hildreth wrote:
not ok 9 - match char
# Failed test 'match char'
# at t/80ora_charset.t line 83.
# got: '?'
# expected
that is set or a patch or lack
thereof on Oracle that might cause it.
I will keep this patch for now in reserve if other people start
complaining about this test
cheers
John Scoles
On Wed, 2008-03-05 at 17:39 -0600, Scott T. Hildreth wrote:
On Thu, 2008-02-14 at 10:03 -0600, Scott T
We have run into an issue with array processing in 11g. The developer
was using execute_array and his sql statement had 'LOG ERRORS' in it.
This did not error out until we switched to 11g. The issue is that only
one is allowed, either 'LOG ERRORS' or 'SAVE EXCEPTIONS'. Our DBA
logged and error
I created this patch because of this issue (which we have run into),
==
Parameter Description
lineReturns a single line of buffered information,
excluding a final newline character. You
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 'LOG ERRORS' in it.
This did not error out until we switched to 11g. The issue is that only
one is allowed
On Tue, 2010-04-06 at 09:51 +0100, Martin Evans wrote:
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
On Fri, 2010-05-21 at 09:23 +0100, Martin Evans wrote:
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
value from Martin J Evans and a bunch of re jigging from
John Scoles
Patch for PL/SQL: numeric or value error: character string buffer too
small from Scott T. Hildreth
Fix for rt.cpan.org Ticket #=51594 type_info and type_info_all miss vital
information from John Scoles
Added
39 matches
Mail list logo
