DBI::Shell and "/"

Is there any way to enter a "/" that's part of the SQL, and not taken as a delimiter? I'm staring at the parsing of the command string, and it appears to accept "\/", except it doesn't rip that \ out, so then I end up with SQL that looks like \/, which the SQL parser doesn't like. Am I just not

RE: DBD

David, > > I got this same error and have seen others post with the same > problem. I d/l'd the whole oracle kit (dbd-oracle-1.14, from > cpan) and built it on my machine, and it works fine (DBI > doesn't have any .dll dependencies that I'm aware of). I > have the full oracle 8.1.4 client in

RE: [dbi] Makefile problems with DBD-ODBC-1.06

No luck with a fresh install. Same errors. I'll try a new download and see what happens. Gary -Original Message- From: Martin J. Evans [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 8:41 AM To: [EMAIL PROTECTED] Subject: RE: [dbi] Makefile problems with DBD-ODBC-1.06 On 12-J

RE: [dbi] Makefile problems with DBD-ODBC-1.06

On 12-Jan-2004 Gary Ebersole wrote: > Thanks, Martin. This fixed the NOOP problem but I still needed to hack > the '*** missing separator' problem in lines 90 and 100. The build now > terminates with ... > > /bin/sh: -c: line 1: unexpected EOF while looking for matching `'' > /bin/sh: -c: line 2:

RE: [dbi] Makefile problems with DBD-ODBC-1.06

Thanks, Martin. This fixed the NOOP problem but I still needed to hack the '*** missing separator' problem in lines 90 and 100. The build now terminates with ... /bin/sh: -c: line 1: unexpected EOF while looking for matching `'' /bin/sh: -c: line 2: syntax error: unexpected end of file make: *** [

inserting strings with NUL chars using DBD::Pg?

DBI 1.37, DBD::Pg 1.31, Perl 5.8.1, PG 7.4.0, Linux. CREATE TABLE t1 (id BYTEA NOT NULL PRIMARY KEY); I can't seem to insert a NUL-containing string to a BYTEA PK column. The string is treated as NUL-terminated so that "123\0001" and "123\0002" are treated as duplicates. I can insert these str

Re: CREATE DATABASE fails in DBD::ADO 2.75-2.83

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: > My current workaround is to shell these commands to osql. Doesn't loc

Re: UNSUBSCRIBING (WAS: RE: ANNOUNCE: DBI 1.40)

On 2004-01-10 12:07:53 -0800, Tim Johnson wrote: > Yes, I was just informed of that by the list admin. Just my $00.02, > but that's the kind of information that should be readily available, > and by readily available I mean in a place that is intuitive to the > user. These days the headers are us

(Fwd) [perl #24846] [PATCH] Apparent utf8 bug in join() in 5.8.[012]

FYI for those using utf8 Tim. - Forwarded message from Slaven Rezic <[EMAIL PROTECTED]> - Delivered-To: [EMAIL PROTECTED] Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm X-List-Archive: Delivered-To: mailing list [EMAIL PROTECTE

Announce: DBD::Ingres-0.51

A minor update: The DBI docs state that swtiching the value of $dbh->{AutoCommit} from off to on should cause a $dbh->commit to be called, but setting $dbh->{ing_rollback} to on will cause a $dbh->rollback to be called instead. This is mainly usefull in situations where you normally have $dbh->{A

ANNOUNCE: DBD::ADO 2.84

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 wh

RE: [dbi] Makefile problems with DBD-ODBC-1.06

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 Ltd, UK Development

RE: CLOB question

Hi Thomas, A couple of suggestions : Firstly, with regard to LongReadLen, the simplest solution is to perform an extra fetch *prior* to your existing one. For example, if your existing fetch is something like this : select col1, col2, ... clob_col from some_table where some_where_clause The

CLOB question

Hi, I wrote a script which does compare the table content of a certain table on different ORACLE-9i databases. For this purpose I fetch all fields from the table in database one and include the fetched values in the WHERE clause for execute the statement at database two. For numeric/char/varchar2 f