Yet Another SQL*Plus Replacement

Tracker: Bugs

5 global commands interpreted in DDL stmts - ID: 586059

Last Update: Comment added ( qzy )

Details:

This is actually a two-part bug.

First, I don't think that the 'global commands' (e.g.
quit, exit, clear, edit) should be allowed anywhere.
If we're in the middle of a DDL statement they should
probably be ignored. Otherwise you never know when
your column definitions will be interpreted as commands.

Second, there is an error in the regexps for the global
commands. I had a column in a table called EditorID,
which was interpreted by yasql as a request to edit the
file 'orID'. If the regexp

$input =~ /^\s*edit\s*(.*)$/i and $nprompt =
edit($1), last SWITCH;

were changed to

$input =~ /^\s*edit\s+(.*)$/i and $nprompt =
edit($1), last SWITCH;

(and similarly for the other commands) the problem
should be resolved.

Submitted:

Nobody/Anonymous ( nobody ) - 2002-07-24 17:46

Priority:

Status:

Closed

Resolution:

None

Assigned:

Nobody/Anonymous

Category:

None

Group:

None

Visibility:

Public

Comments ( 2 )

Date: 2005-05-10 12:43 Sender: qzy Logged In: YES user_id=1209168 Hi there! This was a major issue of the parser code, which has just been fixed, so hopefully ot's gonna be okay for you as well.
Date: 2005-01-05 20:19 Sender: nobody Logged In: NO By Scott Marlowe (smarlowe@g2switchworks.com) I agree with the above. I think that "global" commands should be restricted to commands that start at the leftmost column with a \ character. Then \edit somefilename on the left hand side would be obviously just that. I too have been bitten by this bug, which points up one of the few bothersome quirks in yasl, but one which makes i almost unusable for me, sadly. Is anyone actively maintaining it? It looks like the last update was some time ago, so we may need new folks to work on it to make things happen. I just moved and don't have a home machine OR a lot of free time while at work to work on this, otherwise I might be tempted to fix it, because it's a damn sight easier to use yasql than Oracle's SQL+

Date: 2005-05-10 12:43
Sender: qzy

Logged In: YES
user_id=1209168

Hi there!

This was a major issue of the parser code, which has just
been fixed, so hopefully ot's gonna be okay for you as well.

Date: 2005-01-05 20:19
Sender: nobody

Logged In: NO

By Scott Marlowe (smarlowe@g2switchworks.com)

I agree with the above. I think that "global" commands
should be restricted to commands that start at the leftmost
column with a \ character. Then \edit somefilename on the
left hand side would be obviously just that.

I too have been bitten by this bug, which points up one of
the few bothersome quirks in yasl, but one which makes i
almost unusable for me, sadly. Is anyone actively
maintaining it? It looks like the last update was some time
ago, so we may need new folks to work on it to make things
happen. I just moved and don't have a home machine OR a lot
of free time while at work to work on this, otherwise I
might be tempted to fix it, because it's a damn sight easier
to use yasql than Oracle's SQL+

Log in to comment.

Attached File

Changes ( 2 )

Field	Old Value	Date	By
status_id	Open	2005-05-10 12:43	qzy
close_date	-	2005-05-10 12:43	qzy

Yet Another SQL*Plus Replacement

Tracker: Bugs

Comments ( 2 )

Log in to comment.

Attached File

No Files Currently Attached

Changes ( 2 )

About SourceForge

Find Software

Develop Software

Community

Help