Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ingres > #3787
| From | Roy Hann <specially@processed.almost.meat> |
|---|---|
| Newsgroups | comp.databases.ingres |
| Subject | Re: GUI vs SQL |
| Date | 2022-01-06 23:37 +0000 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <sr7ugf$88d$1@gioia.aioe.org> (permalink) |
| References | <66b44f96-cf00-4b64-b687-47a670965de7n@googlegroups.com> |
Rich Ford wrote: > Is there any consensus over using a tool like DBeaver or just using sql > from the command line? I use 'em both. I definitely use sql more though. The main reason I use DBeaver is when I have to see entire rows that would fold in sql. That's only a slight convenience, not a knock-out punch. And because I need to use sql for scripting anyway I usually already have it running. Also sql starts up in a trice. The compelling argument for using sql is you can display query plans in it, which you can't in DBeaver. (I do wish Ingres would treat QEPs as a core feature instead of delivering them like stowaways hidden in the wheel-well, but...) Roy
Back to comp.databases.ingres | Previous | Next — Previous in thread | Find similar
GUI vs SQL Rich Ford <richford990@gmail.com> - 2022-01-06 13:39 -0800 Re: [Info-ingres] GUI vs SQL Karl Schendel <schendel@kbcomputer.com> - 2022-01-06 17:33 -0500 Re: GUI vs SQL Roy Hann <specially@processed.almost.meat> - 2022-01-06 23:37 +0000
csiph-web