|
Home > Archive > SQL Anywhere Feedback > July 2005 > Enhance ISQLs history
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Enhance ISQLs history
|
|
| Martin Baur 2005-07-03, 9:23 am |
| Hi
I would like ISQL to only put *correct* SQL statements to the statement history.
Now that ISQL saves that history over sessions, the history gets messed up with all my tries to write correct sql statements ...
--
Martin Baur
MindPower.com, IT-Services
| |
| Andrew Giulinn 2005-07-03, 8:23 pm |
| Ooooh no. Maybe have a switch (to either only save correct SQL or to only
show correct SQL) but definitely don't remove the ability to keep incorrect
statements in the history. Admittedly frustrating at times (sometimes an
incorrect statement is recalled), but needed other times (sometimes the
incorrect statement is the closest thing to what is wanted, so recall it and
make the smaller change).
Regarding your request though - what if it was incorrect SQL at the time but
is now valid, eg schema change performed since has now made the SQL correct?
Should the statement (invalid at the time but now valid) show in the history
or not? I would want it to show (assuming that is why I made the schema
change) - but does that mean that ISQL would need to check that the SQL was
valid before showing it in the history?
--
Andrew Giulinn
Senior Analyst/Programmer
Integrated Aviation Software Pty Ltd
"Martin Baur" <tinu@mindpower.com> wrote in message
news:MPG. 1d3205f0ef0701669898
12@forums.sybase.com...
> Hi
>
> I would like ISQL to only put *correct* SQL statements to the statement
> history.
>
> Now that ISQL saves that history over sessions, the history gets messed up
> with all my tries to write correct sql statements ...
>
> --
> Martin Baur
>
> MindPower.com, IT-Services
| |
| Martin Baur 2005-07-04, 3:23 am |
| In article <42c87c25@forums-1-dub>, NO.oscar.SPAM@dsa.com.au says...
> Ooooh no. Maybe have a switch (to either only save correct SQL or to only
Ok, let's have a switch. typos (which are in my case most of my errors) cause my history to get bad.
--
Martin Baur
MindPower.com, IT-Services
| |
| Breck Carter [TeamSybase] 2005-07-04, 1:23 pm |
| Command History doesn't help? I don't use it myself, but it seems you
could use it to pick and choose entries.
I agree with Andrew; I make lots of mistakes but I want to see them
all :)
Breck
On 3 Jul 2005 19:04:40 -0700, Martin Baur <tinu@mindpower.com> wrote:
>In article <42c87c25@forums-1-dub>, NO.oscar.SPAM@dsa.com.au says...
>
>Ok, let's have a switch. typos (which are in my case most of my errors) cause my history to get bad.
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
| |
| Breck Carter [TeamSybase] 2005-07-04, 8:23 pm |
| Heyyyy, Command History is way cool... apparently I've missed the
obvious for years :)
Breck
On 4 Jul 2005 10:26:12 -0700, "Breck Carter [TeamSybase]"
< NOSPAM__bcarter@risi
ngroad.com> wrote:
[color=darkred]
>Command History doesn't help? I don't use it myself, but it seems you
>could use it to pick and choose entries.
>
>I agree with Andrew; I make lots of mistakes but I want to see them
>all :)
>
>Breck
>
>On 3 Jul 2005 19:04:40 -0700, Martin Baur <tinu@mindpower.com> wrote:
>
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
| |
| Andrew Giulinn 2005-07-04, 8:23 pm |
| Always nice to find something new, eh Breck?
I think that Command History is what Martin was referring to - he didn't
want to have to wade through the list looking for the "correct" SQL. Which
is fair enough when that is what you are looking for - but that isn't always
what I am looking for!
I really only started using Command History when I moved to ASA9 (from ASA7)
and found that it kept history between sessions. Very nice thankyou! But
that nice new feature appears to be contributing to Martin's difficulties.
Martin - did you see that you can remove things from the Command History?
Open the Command History window, highlight any statements you don't want to
keep and click on the red cross. That might be enough for you.
Cheers
Andrew
"Breck Carter [TeamSybase]" < NOSPAM__bcarter@risi
ngroad.com> wrote in
message news:23bjc1hcfqa7ga7
4ttku0psitbk4smjprd@
4ax.com...
> Heyyyy, Command History is way cool... apparently I've missed the
> obvious for years :)
>
> Breck
>
> On 4 Jul 2005 10:26:12 -0700, "Breck Carter [TeamSybase]"
> < NOSPAM__bcarter@risi
ngroad.com> wrote:
>
>
> --
> SQL Anywhere Studio 9 Developer's Guide
> Buy the book:
> http://www.amazon.com/exec/obidos/A...7/risingroad-20
> bcarter@risingroad.com
> RisingRoad SQL Anywhere and MobiLink Professional Services
> www.risingroad.com
| |
| Martin Baur 2005-07-05, 7:23 am |
| > Martin - did you see that you can remove things from the Command History?
> Open the Command History window, highlight any statements you don't want to
> keep and click on the red cross. That might be enough for you.
Hi Andrew
Of course I see and use that one can manipulate the history. Fortunately, there are even keyboard shortcuts like ALT-LEFT and ALT-RIGHT to browse through the history - not only the arrow button.
Quick and easy.
However, the display of an complex SQL statement is bad in the history because the SQL got flattened, i.e. is printed on one line. This way, finding the correct statement is not easy when one entered
the statement on multiple lines.
Martin
| |
| Breck Carter [TeamSybase] 2005-07-05, 7:23 am |
| On 4 Jul 2005 18:03:04 -0700, "Andrew Giulinn"
<NO.oscar.SPAM@dsa.com.au> wrote:
>it kept history between sessions. Very nice thank you!
Oh yes, that's a great feature. I've used it to recover SQL scripts
lost when my steenking laptop skips "low battery stand by" and goes
straight to shut down :)
Breck
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
| |
| Andrew Giulinn 2005-07-05, 8:23 pm |
| You are correct Martin. One of the difficulties in using the history is the
"flattening" of complex SQL statements. Maybe an easy "expand to view"
option is required.
"Martin Baur" <tinu@mindpower.com> wrote in message
news:MPG. 1d348d70d885a0898981
7@forums.sybase.com...
>
> Hi Andrew
>
> Of course I see and use that one can manipulate the history. Fortunately,
> there are even keyboard shortcuts like ALT-LEFT and ALT-RIGHT to browse
> through the history - not only the arrow button.
> Quick and easy.
>
> However, the display of an complex SQL statement is bad in the history
> because the SQL got flattened, i.e. is printed on one line. This way,
> finding the correct statement is not easy when one entered
> the statement on multiple lines.
>
> Martin
| |
| Breck Carter [TeamSybase] 2005-07-06, 9:23 am |
| On 5 Jul 2005 18:22:04 -0700, "Andrew Giulinn"
<NO.oscar.SPAM@dsa.com.au> wrote:
>You are correct Martin. One of the difficulties in using the history is the
>"flattening" of complex SQL statements. Maybe an easy "expand to view"
>option is required.
And/or an option to do what Martin originally requested: eliminate
entries that ended in failure when first run... perhaps a "show/hide"
option.
Breck
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
| |
| Jason Hinsperger \(iAnywhere\) 2005-07-06, 1:23 pm |
| What about having DBISQL somehow distinguish between 'correct' and
'incorrect' statements? Would this address your requirement?
eg. Any statement which executed with a SQLCode < 0 (error) is listed in
red text in the history window, while any statement executed with a SQLCode
> 0 (warning) is listed in yellow text in the history window, and any
statement executed with a SQLCode of 0 is listed in green in the history
window.
Just a thought.
--
Jason Hinsperger
Product Manager
iAnywhere Solutions
********************
********************
********************
For the latest downloads technotes, whitepapers, webcasts and other
developer
resources, go to: http://www.ianywhere.com/developer/
********************
********************
********************
"Breck Carter [TeamSybase]" < NOSPAM__bcarter@risi
ngroad.com> wrote in
message news:o1onc1d4k5u48oa
sjtrfolp294f89i0n6i@
4ax.com...
> On 5 Jul 2005 18:22:04 -0700, "Andrew Giulinn"
> <NO.oscar.SPAM@dsa.com.au> wrote:
>
>
> And/or an option to do what Martin originally requested: eliminate
> entries that ended in failure when first run... perhaps a "show/hide"
> option.
>
> Breck
>
> --
> SQL Anywhere Studio 9 Developer's Guide
> Buy the book:
> http://www.amazon.com/exec/obidos/A...7/risingroad-20
> bcarter@risingroad.com
> RisingRoad SQL Anywhere and MobiLink Professional Services
> www.risingroad.com
| |
| Breck Carter [TeamSybase] 2005-07-06, 1:23 pm |
| Even better, IMO :)
Martin?
On 6 Jul 2005 10:08:36 -0700, "Jason Hinsperger \(iAnywhere\)"
< NOjason_hinspergerSP
AM@hotmail.com> wrote:
>What about having DBISQL somehow distinguish between 'correct' and
>'incorrect' statements? Would this address your requirement?
>
>eg. Any statement which executed with a SQLCode < 0 (error) is listed in
>red text in the history window, while any statement executed with a SQLCode
>statement executed with a SQLCode of 0 is listed in green in the history
>window.
>
>Just a thought.
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
| |
| Martin Baur 2005-07-07, 3:24 am |
| In article < 2j4oc11ji7tap5jqhjj1
j1ji568m4lhs9n@4ax.com>, NOSPAM__bcarter@risi
ngroad.com says...[color=darkred]
> Even better, IMO :)
>
> Martin?
>
I'd take that .. :-) ... it'll be quite helpful I guess.
So, when?
Regards to all
Martin
| |
| Andrew Giulinn 2005-07-07, 3:24 am |
| Can I request something to help the colourblind among us, eg some sort of
shape, coloured as you suggest?
Other than that, your idea sounds good.
Cheers
Andrew
"Jason Hinsperger (iAnywhere)" < NOjason_hinspergerSP
AM@hotmail.com> wrote in
message news:42cc1014$1@foru
ms-1-dub...
> What about having DBISQL somehow distinguish between 'correct' and
> 'incorrect' statements? Would this address your requirement?
>
> eg. Any statement which executed with a SQLCode < 0 (error) is listed in
> red text in the history window, while any statement executed with a
> SQLCode
> statement executed with a SQLCode of 0 is listed in green in the history
> window.
>
> Just a thought.
>
> --
> Jason Hinsperger
> Product Manager
> iAnywhere Solutions
> ********************
********************
********************
> For the latest downloads technotes, whitepapers, webcasts and other
> developer
> resources, go to: http://www.ianywhere.com/developer/
> ********************
********************
********************
>
>
>
> "Breck Carter [TeamSybase]" < NOSPAM__bcarter@risi
ngroad.com> wrote in
> message news:o1onc1d4k5u48oa
sjtrfolp294f89i0n6i@
4ax.com...
>
>
|
|
|
|
|