| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
| Cc: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com>, "A B" <gentosaker(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Annoying messages when copy sql code to psql terminal |
| Date: | 2008-06-06 17:05:42 |
| Message-ID: | dcc563d10806061005r72c424d8xa375350e8345a450@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jun 6, 2008 at 6:12 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Fri, Jun 6, 2008 at 12:39 AM, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> wrote:
>> On Fri, Jun 6, 2008 at 7:58 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>>> As others have noted, you have tabs in your sql source. I'd advise if
>>> possible, not to use the tab character in sql, for this and other
>>> reasons.
>>
>> Can you please elaborate on other reasons? I have never encountered any
>> _other_ reason!!
>>
>> And 'using psql' is not reason enough to not indent your SQL code.
>
> For example, another reason tabs are annoying are how your function
> sources show up in '\df+' (escaped). iirc you can get around this
> with '\x', but why bother with that? Also, I am not suggesting not to
> indent your sql, just not to use the tab character.
Almost every decent text editor has the option to use spaces in place
of tabs. Even Nano can do it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Reece Hart | 2008-06-06 17:13:53 | Re: Annoying messages when copy sql code to psql terminal |
| Previous Message | Scott Marlowe | 2008-06-06 17:01:24 | Re: when to reindex? |