<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>> when I have to see entire rows that would fold in sql. That's only a slight convenience<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>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.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>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.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>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.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><img width=390 height=491 style='width:4.0625in;height:5.1145in' id="Picture_x0020_1" src="cid:image001.png@01D803A8.5C3E85A0"><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>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.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Column and table name auto-suggestion would be nice too along with syntax hints – but I get by with plain old sql/tm<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><span lang=EN-US style='mso-fareast-language:EN-GB'>-----Original Message-----<br>From: info-ingres-bounces@lists.planetingres.org <info-ingres-bounces@lists.planetingres.org> On Behalf Of Roy Hann<br>Sent: 06 January 2022 23:38<br>To: info-ingres@lists.planetingres.org<br>Subject: Re: [Info-ingres] GUI vs SQL</span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Rich Ford wrote:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> Is there any consensus over using a tool like DBeaver or just using <o:p></o:p></p><p class=MsoPlainText>> sql from the command line?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I use 'em both. I definitely use sql more though. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>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.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>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...)<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Roy<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>_______________________________________________<o:p></o:p></p><p class=MsoPlainText>Info-ingres mailing list<o:p></o:p></p><p class=MsoPlainText><a href="mailto:Info-ingres@lists.planetingres.org"><span style='color:windowtext;text-decoration:none'>Info-ingres@lists.planetingres.org</span></a><o:p></o:p></p><p class=MsoPlainText><a href="https://lists.planetingres.org/mailman/listinfo/info-ingres"><span style='color:windowtext;text-decoration:none'>https://lists.planetingres.org/mailman/listinfo/info-ingres</span></a><o:p></o:p></p></div></body></html>