Re: DBI::Shell and "/"
From: Thomas A. Lowery (tlowery_at_rparts.us)
Date: 01/14/04
- Previous message: Jeff Urlwin: "RE: DBD::ADO and ODBC Information Code"
- In reply to: Randal L. Schwartz: "Re: DBI::Shell and "/""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 13 Jan 2004 21:52:05 -0500 To: dbi-users@perl.org
On Tue, Jan 13, 2004 at 10:13:44AM -0800, Randal L. Schwartz wrote:
> >>>>> "Tim" == Tim Bunce <Tim.Bunce@pobox.com> writes:
>
> Tim> On Mon, Jan 12, 2004 at 04:00:28PM -0800, Randal L. Schwartz wrote:
> >>
> >> 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 seeing something, or is this a bug?
>
> Tim> Sounds like a bug. Are you using the DBI::Shell that comes with the DBI
> Tim> or the (much improved) one from CPAN?
>
> I'm using:
>
> It looks like there's code in there that *tries* to get
> the slashing right, by permitting a backslash, but I haven't
> traced down why it's not doing the right thing. It seems to keep
> handing the backslash to the SQL parser, which is wrong.
>
> I post here because I want to know if anyone else has seen this behavior,
> or if it's just me. :)
This something I haven't been able to fix.
Currently the only way to do something like select 5 / 6 /
is to set the command prefix to a different value.
/opt command_prefix=;
Help solving this problem and/or patches are welcome!
Tom
- Previous message: Jeff Urlwin: "RE: DBD::ADO and ODBC Information Code"
- In reply to: Randal L. Schwartz: "Re: DBI::Shell and "/""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]