6 comments

BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

+1, not lazy sometimes too much to type.

SQL Plugin is truly top notch though, good work.

R

Libor Valenta wrote:

| Call me lazy, but autocomplete for keywords, table names and column
names will be really cool :)
-


BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/zM4o+cV9vuB27SARApbEAKDHyRRKWOakx9f4VXoN1N/shQldygCgr3v4
cDLYqWkIxZppG9HcOta9Vfg=
=C1H3
-


END PGP SIGNATURE-----

0

Would be nice to have query history and each tab should remember the last database been selected to execute the query

0

BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hum yes, plus hold the query history on a per project basis so even
after we quit and go back to the project, we can still look at the
history and re run the queries over again if we need to. It gets real
old typing SQL... even in class files.

R

Vladimir Goncharov wrote:

| Would be nice to have query history and each tab should remember the
last database been selected to execute the query
-


BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/zN7/+cV9vuB27SARAtdTAJ42LcbRJYSnXW2mq16AF20arkLK2ACgkVc6
i8rr7Cxmn62t4qgRj8EUOUw=
=//od
-


END PGP SIGNATURE-----

0

I already thought about implementing such a feature but I have to implement a complete SQL Parser
which understands at least the standard SQL syntax. Even such a standard-SQL parser is a lot of
work but most databases use a slightly changed SQL syntax so I either have parsable code and non-parsable
code in one string or I have to implement an parser for each database. Both would be very difficult to
handle.

I could implement a user-controlled autocomplete such that I open different lookups (one for keywords, one for
table and one for columns) with different keybord shortcuts.

Bye, Stefan.

Robert S. Sfeir wrote:

---BEGIN PGP SIGNED MESSAGE---
Hash: SHA1

+1, not lazy sometimes too much to type.

SQL Plugin is truly top notch though, good work.

R

Libor Valenta wrote:

| Call me lazy, but autocomplete for keywords, table names and column
names will be really cool :)
---BEGIN PGP SIGNATURE---
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/zM4o+cV9vuB27SARApbEAKDHyRRKWOakx9f4VXoN1N/shQldygCgr3v4
cDLYqWkIxZppG9HcOta9Vfg=
=C1H3
---END PGP SIGNATURE---


0

You have the option to save all open queries into the workspace file. So all you have
to do is to enable the option and open a new query if you don't want to modify the current
query.

Bye, Stefan.

Robert S. Sfeir wrote:

---BEGIN PGP SIGNED MESSAGE---
Hash: SHA1

Hum yes, plus hold the query history on a per project basis so even
after we quit and go back to the project, we can still look at the
history and re run the queries over again if we need to. It gets real
old typing SQL... even in class files.

R

Vladimir Goncharov wrote:

| Would be nice to have query history and each tab should remember the
last database been selected to execute the query
---BEGIN PGP SIGNATURE---
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/zN7/+cV9vuB27SARAtdTAJ42LcbRJYSnXW2mq16AF20arkLK2ACgkVc6
i8rr7Cxmn62t4qgRj8EUOUw=
=//od
---END PGP SIGNATURE---


0

Lookups will be fine, for keywords should be simple, for tables probably also, but columns - it must be filtered to tables used in query to be useful, this will probably require parsing SQL.
I vote 10 for table lookup. (If is possible overload standard shortcut in one window, I suggest CtrlN)

0

Please sign in to leave a comment.