RE: DBI (1.32, 1.37) transforms data before passing it to the driver? (XML and UTF-8 getting in the way?)

Jonathan, Yes, 'encode' works. I realize the problem isn't really fixed, but it's fixed enough for this humble (and humbled) Applications Programmer/DBA. Thank you to everyone, Jay Jay Konigsberg Database Administrator TowerRecords.com (916) 373-2406Fax: (916) 373-2930 [EMAIL PROTECTED]

Re: DBI (1.32, 1.37) transforms data before passing it to the driver? (XML and UTF-8 getting in the way?)

I'm glad you've found something that works. But can someone summarise the causes/issues into something we can all understand? [I don't have time to try to do that for myself.] Obviously the current situation is not good. But I need to have a better understanding of *exactly* what's going on at

Re: i know it's utf-8, how can i force perl to see it that way

[moved to dbi-users] On Wed, Jun 18, 2003 at 02:48:29PM +0200, Brigitte Jellinek wrote: On Mon, Jun 16, 2003 at 10:10:52AM -0400, Nathaniel W. Turner wrote: The crux of the problem is that mysql thinks it knows what it's doing, and is assuming incoming data is latin1*, and thus storing your

RE: DBD-Ingres problem on Solaris - SOLUTION plus followup questi on

All, In the hope that this will help others... I have solved my problem with DBD-Ingres on Solaris. The problem was that DBD-Ingres was apparently making correctly, but make test failed with a dynamic linking problem. I beat my head against this for several days, trying different versions of

Re: DBI (1.32, 1.37) transforms data before passing it to the driver? (XML and UTF-8 getting in the way?)

Tim Bunce [EMAIL PROTECTED] writes: But can someone summarise the causes/issues into something we can all understand? [I don't have time to try to do that for myself.] Since we went through the utf8 story and I believe we now understand it fully, I ought to at least try. As I see it, the core

Re: Database layout and query questions...

I personally think Paul Dubois's book MySQL does a good job not only covering all aspects of MySQL installation, setup, and maintenance, but I think it also gives a very good introduction on table design right in Chapter 1 (I have the 1st MySQL - I see on Paul's homepage

Re: Query formatting problem

replacing ? for '500' replacing ? for '500' replacing ? for '12-Jul-2003' SELECT foo, bar FROM some_table WHERE name='500', AND value='500', AND date='12-Jul-2003' Sorry, but this fails in our database. See, the first use of 500 is in a varchar, the second in an

DBD::Oracle ppm availability

Does anyone know where I might find a DBD::Oracle ppm for use with Activestate's perl distro for Windows? The list archives make frequent reference to a ppm repository at xmlproj.com, and then mention some sort of domain name dispute or hijacking (which seems to be still in dispute, or else

Re: Query formatting problem

I did this example with a Oracle connection. I am using the quote method from my database handle. The quoting will be specific to your database. I just tried it with MySQL. No problem there either. What db are you using? What errors is it throwing? Steven Lembark wrote: replacing ? for '500'

RE: sql problem

I know that at least with MySQL you can use: SELECT database1.table1.field1, database1.table.2.field1, database2.table1.field1, database2.table2.field1 FROM database1.table1, database1.table2, database2.table1, database2.table2 WHERE ... --TWH -Original Message- From: Pascal Gravot

$sth-execute and $dbh-do hung on Updating Oracle DB

list, I wrote a simple test script to update Oracle database, but it hung on the line of $dbh-do($sql2). Oracle server: NT, oracle version 8.0.3 my script running on W2000, with perl 5.6.1.633, DBD-ORACLE and DBI 1.34 The select statement $sql1 works fine, but the script hung on the line of

Re: DBI (1.32, 1.37) transforms data before passing it to the driver? (XML and UTF-8 getting in the way?)

On Thursday, June 19, 2003, at 02:00 AM, Tim Bunce wrote: But can someone summarise the causes/issues into something we can all understand? [I don't have time to try to do that for myself.] I see it this way: In the past, even with UTF-8 enabled versions of Perl, UTF-8 was never an issue because

Re: $sth-execute and $dbh-do hung on Updating Oracle DB

On Thu, Jun 19, 2003 at 10:46:56AM -0600, Chang, Mei wrote: I wrote a simple test script to update Oracle database, but it hung on the line of $dbh-do($sql2). Oracle server: NT, oracle version 8.0.3 my script running on W2000, with perl 5.6.1.633, DBD-ORACLE and DBI 1.34 The select

Re: DBI (1.32, 1.37) transforms data before passing it to the driver? (XML and UTF-8 getting in the way?)

On Thursday, June 19, 2003, at 02:00 AM, Tim Bunce wrote: But can someone summarise the causes/issues into something we can all understand? [I don't have time to try to do that for myself.] I'm attaching some code that may shed some light on this: The program sets up $string_1 as a byte string,

RE: $sth-execute and $dbh-do hung on Updating Oracle DB

Ronald, good point. I forgot to run commit via a sqlplus session. It works now. Can DBI generate an error string instead of hanging for a situation like this? Thanks a lot for your help. Chang -Original Message- From: Ronald J Kimball [mailto:[EMAIL PROTECTED] Sent: Thursday, June

RE: Can't build DBD::Oracle on AIX 5.1 with Oracle 9.2

Bjorn: I intend to write a brief 'howto' with all the details on it, but in short: -use Perl 5.8.0 (the latest stable from CPAN) -use the xlc_r version of IBM's compiler and build 32 bit Perl. All tests should be successfull. -get and install DBI -get DBD::Oracle. Edit the Makefile.PL or

RE: [dbi] Force ODBC version 2 behavior

Yup that did the trick. I found this blurb about odbc_version, but I implemented it incorrectly when I tried it before... maybe this will help somebody in the future. i.e. I had a connection similar to this: my $cs =

Re: $sth-execute and $dbh-do hung on Updating Oracle DB

Chang, Mei wrote: good point. I forgot to run commit via a sqlplus session. It works now. Can DBI generate an error string instead of hanging for a situation like this? It's not an error condition to be waiting on other session's lock; and it wouldn't be DBI's responsibility anyway, it's

RE: Database layout and query questions...

On Wed, 18 Jun 2003 09:34:11 -0500, NIPP, SCOTT V (SBCSI) wrote: Hi Scott We're drifting off-topic, so I'll just give a schema below and then fade away... Let's say that I have users Mary, Joe, Frank, and Dan. I also have servers panther, cheetah, jaguar and lion. The data for each

Re: DBI (1.32, 1.37) transforms data before passing it to the driver? (XML and UTF-8 getting in the way?)

To follow up on Tom's good examples, which I believe were run on Perl 6, I decided to try with Perl 5.8.0, and I found that version of Perl _is_ indeed a lot better. In Perl 5.8, the idea is that the internal representation (single-byte or utf8) should not be visible to the programmer. So Perl

RE: No error string and unitialized value in concatenation

Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/site_perl/5.6.1/i686-linux/DBI.pm line 584. DBI connect('testviagamb','Fred',...) failed: at ./con.pl line 6 $drh-errstr is returning undef: connect DISPATCH (DBI::dr=HASH(0x81bb28c) rc2/3 @5

FW: CPAN Upload: J/JU/JURL/DBD-ODBC-1.06.tar.gz

Fixed test in t/02simple.t to skip if the DSN defined by the user has DSN= in it. Added tests for wrong DSN, ensuring the DBI::errstr is appropriately set. Fixed small issue in Makefile.PL for Unix systems thanks to H.Merijn Brand. Update to NOT copy user id and password to connect string if