[Info-ingres] GUI vs SQL

Martin Bowes martin.bowes at ndph.ox.ac.uk
Fri Jan 7 09:30:31 UTC 2022


Try using the \vert command in tm to improve the display of character fields over 80 columns.

Eg.
* \vert
* select table_owner, table_name from iitables\g
Executing . . .

**** Row : 1 ****
table_owner : $ingres
table_name : iirole

**** Row : 2 ****
table_owner : $ingres
table_name : ii_atttype

etc.

Marty

From: Adrian Williamson <adrian.williamson at rationalcommerce.com>
Sent: 07 January 2022 09:25
To: 'Roy Hann' <specially at processed.almost.meat>; info-ingres at lists.planetingres.org
Subject: Re: [Info-ingres] GUI vs SQL


> when I have to see entire rows that would fold in sql. That's only a slight convenience



I use sql as well - I never know when I might be in a situation where I do not have any tools of preference to hand, so I use the basics.



I use MS windows by default, so I always change the Properties for command prompts so that the Screen buffer size has a width of 2K which helps to keep wrapping to a minimum.



I figure what I can't work out in 2k needs me to start specifying column names sometimes with varchar(colname,50) casts just to keep it legible.



[cid:image001.png at 01D803A9.36C89120]



I often remark that I would like a command line based AI that learns about my border line dyslexia / crap spelling and will correct me as I go.



Column and table name auto-suggestion would be nice too along with syntax hints - but I get by with plain old sql/tm





-----Original Message-----
From: info-ingres-bounces at lists.planetingres.org<mailto:info-ingres-bounces at lists.planetingres.org> <info-ingres-bounces at lists.planetingres.org<mailto:info-ingres-bounces at lists.planetingres.org>> On Behalf Of Roy Hann
Sent: 06 January 2022 23:38
To: info-ingres at lists.planetingres.org<mailto:info-ingres at lists.planetingres.org>
Subject: Re: [Info-ingres] GUI vs SQL



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



_______________________________________________

Info-ingres mailing list

Info-ingres at lists.planetingres.org<mailto:Info-ingres at lists.planetingres.org>

https://lists.planetingres.org/mailman/listinfo/info-ingres
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.planetingres.org/pipermail/info-ingres/attachments/20220107/0810671b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 17065 bytes
Desc: image001.png
URL: <https://lists.planetingres.org/pipermail/info-ingres/attachments/20220107/0810671b/attachment-0001.png>


More information about the Info-ingres mailing list