From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | Charles Clavadetscher <clavadetscher(at)swisspug(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, dandl <david(at)andl(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Ascii Elephant for text based protocols |
Date: | 2016-05-16 03:56:55 |
Message-ID: | CANu8FiymZUcLHQYJGLuorBhMyzQPqJKHuQpvw5iRmvDLCy9JXA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, May 15, 2016 at 11:47 PM, Charles Clavadetscher <
clavadetscher(at)swisspug(dot)org> wrote:
> Hello Tom
>
> Thanks for your feedback.
>
> On 05/16/2016 05:31 AM, Tom Lane wrote:
>
>> Charles Clavadetscher <clavadetscher(at)swisspug(dot)org> writes:
>>
>>> On 05/16/2016 02:51 AM, dandl wrote:
>>>
>>>> * the trunk is (how shall I put this?) somewhat phallic.
>>>>
>>>
>> Mmh... This could apply to any elephant picture. I don't think that this
>>> needs a change, but let's see if there are more feedbacks.
>>>
>>
>> I'd say the problem is at the end: elephant trunks don't curve that
>> direction.
>>
>
> True. I let myself lead more by the original picture than by zoology.
>
> Instead of
>>
>> | v | | v |
>>> | \__/ |
>>>
>>
>> maybe
>>
>> | v | | v |
>>> | |__| |
>>>
>>
>> or even
>>
>> | v | | v |
>>> | |/\| |
>>>
>>
> The second variant seems better. Now it looks like this.
>
> ____ ______ ___
> / )/ \/ \
> ( / __ _\ )
> \ (/ o) ( o) )
> \_ (_ ) \ ) _/
> \ /\_/ \)/
> \/ <//| |\\>
> | |
> |/\|
>
> Have a good day.
> Charles
>
>
>
>> regards, tom lane
>>
>
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
To all, thanks for the concept. The following based on original design
submission, might help in tweaking:
CREATE TABLE elephant
(row_num integer NOT NULL,
row_dat varchar(30) NOT NULL,
CONSTRAINT elephant_pk PRIMARY KEY (row_num)
);
INSERT INTO elephant
(row_num, row_dat)
VALUES
( 1,'+------------------------+'),
( 2,'| ____ ______ ___ |'),
( 3,'| / )/ \/ \ |'),
( 4,'| ( / __ _\ ) |'),
( 5,'| \ (/ o) ( o) ) |'),
( 6,'| \_ (_ ) \ ) / |'),
( 7,'| \ /\_/ \)_/ |'),
( 8,'| \/ //| |\\ |'),
( 9,'| v | | v |'),
(10,'| \__/ |'),
(11,'| |'),
(12,'| PostgreSQL 1996-2016 |'),
(13,'| 20 Years of success |'),
(14,'+------------------------+');
SELECT row_dat FROM elephant ORDER BY row_num;
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Charles Clavadetscher | 2016-05-16 04:36:50 | Re: Ascii Elephant for text based protocols |
Previous Message | Charles Clavadetscher | 2016-05-16 03:47:26 | Re: Ascii Elephant for text based protocols |