Re: New mug design

bruce wrote:
> Thom Brown wrote:
> > 2009/11/16 damien clochard <damien(at)dalibo(dot)info>:
> > > Josh Berkus a ?crit :
> > >> ADS,
> > >>
> > >> Just an elephant-logo mug probably won't go very far here; we were
> > >> practically forcing the EDB mugs on people (for free) once we got to the
> > >> last box.
> > >>
> > >> Idea for a new mug design: do an instructional one of psql shortcuts,
> > >> per the vi coffee mug:
> > >>
> > >
> > > Why not : ?INSERT INTO me VALUES('coffee','sugar');
> > >
> >
> > That's a great suggestion! :)
>
> INSERT INTO pg_mug VALUES('coffee', 'sugar', 'cream');

Or we could highlight our transacitonal DDL:

BEGIN;
CREATE TABLE postgresql (mug_id SERIAL);
COMMIT;

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On Sat, 28 Nov 2009, Bruce Momjian wrote:

> bruce wrote:
>> Thom Brown wrote:
>>> 2009/11/16 damien clochard <damien(at)dalibo(dot)info>:
>>>> Josh Berkus a ?crit :
>>>>> ADS,
>>>>>
>>>>> Just an elephant-logo mug probably won't go very far here; we were
>>>>> practically forcing the EDB mugs on people (for free) once we got to the
>>>>> last box.
>>>>>
>>>>> Idea for a new mug design: do an instructional one of psql shortcuts,
>>>>> per the vi coffee mug:
>>>>>
>>>>
>>>> Why not : ?INSERT INTO me VALUES('coffee','sugar');
>>>>
>>>
>>> That's a great suggestion! :)
>>
>> INSERT INTO pg_mug VALUES('coffee', 'sugar', 'cream');
>
> Or we could highlight our transacitonal DDL:
>
> BEGIN;
> CREATE TABLE postgresql (mug_id SERIAL);
> COMMIT;

Add the INSERT INTO before the COMMIT ... ? So that its complete?

----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scrappy(at)hub(dot)org http://www.hub.org

Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy(at)hub(dot)org

I suggest that you combine the two ideas:

>>> INSERT INTO pg_mug VALUES('coffee', 'water', 'sugar', 'cream');

And

>> BEGIN;
>> CREATE TABLE postgresql (mug_id SERIAL);
>> COMMIT;

Regards

Rob Napier

Rob Napier wrote:
> I suggest that you combine the two ideas:
>
> >>> INSERT INTO pg_mug VALUES('coffee', 'water', 'sugar', 'cream');
>
> And
>
> >> BEGIN;
> >> CREATE TABLE postgresql (mug_id SERIAL);
> >> COMMIT;

You mean:

BEGIN;
CREATE TABLE pg_mug (contents TEXT);
INSERT INTO pg_mug VALUES('coffee', 'sugar', 'cream');
COMMIT;

?

I don't think "water" makes sense unless you are making instant coffee,
which I think is atypical.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Hello,

On Sat, 28 Nov 2009 16:39:25 -0500 (EST) Bruce Momjian wrote:

> Rob Napier wrote:
> > I suggest that you combine the two ideas:
> >
> > >>> INSERT INTO pg_mug VALUES('coffee', 'water', 'sugar', 'cream');
> >
> > And
> >
> > >> BEGIN;
> > >> CREATE TABLE postgresql (mug_id SERIAL);
> > >> COMMIT;
>
> You mean:
>
> BEGIN;
> CREATE TABLE pg_mug (contents TEXT);
> INSERT INTO pg_mug VALUES('coffee', 'sugar', 'cream');
> COMMIT;
>
> ?

+1

But we need to linebreak the third line, else it will go around
the mug (and i want the logo on the other side). So this results
in 5 lines SQL-code, that's ok.

What about the "SELECT PostgreSQL();" idea mentioned upthread?

Bye

--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project

On Sat, 28 Nov 2009, Bruce Momjian wrote:

> Rob Napier wrote:
>> I suggest that you combine the two ideas:
>>
>>>>> INSERT INTO pg_mug VALUES('coffee', 'water', 'sugar', 'cream');
>>
>> And
>>
>>>> BEGIN;
>>>> CREATE TABLE postgresql (mug_id SERIAL);
>>>> COMMIT;
>
> You mean:
>
> BEGIN;
> CREATE TABLE pg_mug (contents TEXT);
> INSERT INTO pg_mug VALUES('coffee', 'sugar', 'cream');
> COMMIT;
>
> ?
>
> I don't think "water" makes sense unless you are making instant coffee,
> which I think is atypical.

Ummm ... last I checked, that query will fail with too many fields? :)

----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scrappy(at)hub(dot)org http://www.hub.org

Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy(at)hub(dot)org

2009/11/28 Marc G. Fournier <scrappy(at)hub(dot)org>

> On Sat, 28 Nov 2009, Bruce Momjian wrote:
>
> Rob Napier wrote:
>>
>>> I suggest that you combine the two ideas:
>>>
>>> INSERT INTO pg_mug VALUES('coffee', 'water', 'sugar', 'cream');
>>>>>>
>>>>>
>>> And
>>>
>>> BEGIN;
>>>>> CREATE TABLE postgresql (mug_id SERIAL);
>>>>> COMMIT;
>>>>>
>>>>
>> You mean:
>>
>> BEGIN;
>> CREATE TABLE pg_mug (contents TEXT);
>> INSERT INTO pg_mug VALUES('coffee', 'sugar', 'cream');
>> COMMIT;
>>
>> ?
>>
>> I don't think "water" makes sense unless you are making instant coffee,
>> which I think is atypical.
>>
>
> Ummm ... last I checked, that query will fail with too many fields? :)
>
>
> I proposed this: http://wiki.postgresql.eu/wiki/Image:Psql-mug.png

Thom

Andreas 'ads' Scherbaum wrote:
> But we need to linebreak the third line, else it will go around
> the mug (and i want the logo on the other side). So this results
> in 5 lines SQL-code, that's ok.
>
>
> What about the "SELECT PostgreSQL();" idea mentioned upthread?

That seems fine too. I think the question is whether we want something
relating to the mug contents, i.e. cute, or something more clearly
referencing PostgreSQL.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Marc G. Fournier wrote:
> > You mean:
> >
> > BEGIN;
> > CREATE TABLE pg_mug (contents TEXT);
> > INSERT INTO pg_mug VALUES('coffee', 'sugar', 'cream');
> > COMMIT;
> >
> > ?
> >
> > I don't think "water" makes sense unless you are making instant coffee,
> > which I think is atypical.
>
> Ummm ... last I checked, that query will fail with too many fields? :)

Yep, only I could inject a bug into a mug. :-(

The correct query is:

BEGIN;
CREATE TABLE pg_mug (contents TEXT);
INSERT INTO pg_mug VALUES('coffee'), ('sugar'), ('cream');
COMMIT;

That highlights our multi-value INSERT too. :-) With proper wrap it
would be:

BEGIN;
CREATE TABLE pg_mug (contents TEXT);
INSERT INTO pg_mug
VALUES('coffee'), ('sugar'), ('cream');
COMMIT;

You can even add stirring:

BEGIN;
CREATE TABLE pg_mug (contents TEXT);
INSERT INTO pg_mug
VALUES('coffee'), ('sugar'), ('cream');
-- stir
SELECT * FROM pg_mug ORDER BY random();
COMMIT;

FYi, I am just shooting out ideas until someone tells me to stop. ;-)

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

that last one is perfect

Sent from my iPhone

On 2009-11-28, at 18:57, Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> Marc G. Fournier wrote:
>>> You mean:
>>>
>>> BEGIN;
>>> CREATE TABLE pg_mug (contents TEXT);
>>> INSERT INTO pg_mug VALUES('coffee', 'sugar', 'cream');
>>> COMMIT;
>>>
>>> ?
>>>
>>> I don't think "water" makes sense unless you are making instant
>>> coffee,
>>> which I think is atypical.
>>
>> Ummm ... last I checked, that query will fail with too many
>> fields? :)
>
> Yep, only I could inject a bug into a mug. :-(
>
> The correct query is:
>
> BEGIN;
> CREATE TABLE pg_mug (contents TEXT);
> INSERT INTO pg_mug VALUES('coffee'), ('sugar'), ('cream');
> COMMIT;
>
> That highlights our multi-value INSERT too. :-) With proper wrap it
> would be:
>
> BEGIN;
> CREATE TABLE pg_mug (contents TEXT);
> INSERT INTO pg_mug
> VALUES('coffee'), ('sugar'), ('cream');
> COMMIT;
>
> You can even add stirring:
>
> BEGIN;
> CREATE TABLE pg_mug (contents TEXT);
> INSERT INTO pg_mug
> VALUES('coffee'), ('sugar'), ('cream');
> -- stir
> SELECT * FROM pg_mug ORDER BY random();
> COMMIT;
>
> FYi, I am just shooting out ideas until someone tells me to stop. ;-)
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + If your life is a hard drive, Christ can be your backup. +

On Nov 28, 2009, at 2:52 PM, Bruce Momjian wrote:

> Andreas 'ads' Scherbaum wrote:
>> What about the "SELECT PostgreSQL();" idea mentioned upthread?
>
> That seems fine too. I think the question is whether we want
> something
> relating to the mug contents, i.e. cute, or something more clearly
> referencing PostgreSQL.

What I particularly liked about:

SELECT PostgreSQL();
COMMIT;

... (even if I do say so myself) is that it is advocacy, and is PG-
specific.

--
-- Christophe Pettus
xof(at)thebuild(dot)com

Whatever kind of coffee you make, you still need some water.

e.g. Outside the USA, very few people use cream (or anything pretending to
be cream).

Even when I make a cappucino I need water to make steam.

I think that we have to expect American culture in the message even though
it is supposed to be targeted at an international market unless you opt for
a more generic message.

Anyway, I think the idea of tying the function of the coffee mug to
PostgreSQL concepts has a lot of merit.

On 29/11/09 8:39 AM, "Bruce Momjian" <bruce(at)momjian(dot)us> wrote:

> Rob Napier wrote:
>> I suggest that you combine the two ideas:
>>
>>>>> INSERT INTO pg_mug VALUES('coffee', 'water', 'sugar', 'cream');
>>
>> And
>>
>>>> BEGIN;
>>>> CREATE TABLE postgresql (mug_id SERIAL);
>>>> COMMIT;
>
> You mean:
>
> BEGIN;
> CREATE TABLE pg_mug (contents TEXT);
> INSERT INTO pg_mug VALUES('coffee', 'sugar', 'cream');
> COMMIT;
>
> ?
>
> I don't think "water" makes sense unless you are making instant coffee,
> which I think is atypical.

Regards

Rob Napier

Rob Napier wrote:
> Whatever kind of coffee you make, you still need some water.

Yes, but you combine the water and the coffee outside the mug. ;-)
Unless we are talking about cheap instant coffee, and we all agree
Postgres should not be associated with cheap, poor-tasting coffee;
there are other databases for that. ;-)

> e.g. Outside the USA, very few people use cream (or anything
> pretending to be cream).

Uh, how come they put milk in tea only outside the USA? As a tea
drinker, I am confused. ;-)

> Even when I make a cappucino I need water to make steam.

Do you do that in the mug?

> I think that we have to expect American culture in the message
> even though it is supposed to be targeted at an international
> market unless you opt for a more generic message.

I didn't realize the cream/milk issue. Is there something else we can
include?

> Anyway, I think the idea of tying the function of the coffee
> mug to PostgreSQL concepts has a lot of merit.

Cool.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On Sat, 28 Nov 2009, Bruce Momjian wrote:

> Rob Napier wrote:
>> Whatever kind of coffee you make, you still need some water.
>
> Yes, but you combine the water and the coffee outside the mug. ;-)
> Unless we are talking about cheap instant coffee, and we all agree
> Postgres should not be associated with cheap, poor-tasting coffee;
> there are other databases for that. ;-)
>
>> e.g. Outside the USA, very few people use cream (or anything
>> pretending to be cream).
>
> Uh, how come they put milk in tea only outside the USA? As a tea
> drinker, I am confused. ;-)
>
>> Even when I make a cappucino I need water to make steam.
>
> Do you do that in the mug?

Use the steam, yes .. make the steam, no ...

----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scrappy(at)hub(dot)org http://www.hub.org

Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy(at)hub(dot)org

Christophe Pettus wrote:
>
> On Nov 28, 2009, at 2:52 PM, Bruce Momjian wrote:
>
> > Andreas 'ads' Scherbaum wrote:
> >> What about the "SELECT PostgreSQL();" idea mentioned upthread?
> >
> > That seems fine too. I think the question is whether we want
> > something
> > relating to the mug contents, i.e. cute, or something more clearly
> > referencing PostgreSQL.
>
> What I particularly liked about:
>
> SELECT PostgreSQL();
> COMMIT;
>
> ... (even if I do say so myself) is that it is advocacy, and is PG-
> specific.

The other side of the mug will have the Postgres elephant and the
PostgreSQL name so I think we can be more subtle on the SQL query side
of the mug.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On Sat, 28 Nov 2009 17:57:38 -0500 (EST) Bruce Momjian wrote:

> FYi, I am just shooting out ideas until someone tells me to stop. ;-)

Keep going, we will sort it out ;-)

--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project

On Sat, 28 Nov 2009 17:57:38 -0500 (EST) Bruce Momjian wrote:

> That highlights our multi-value INSERT too. :-) With proper wrap it
> would be:
>
> BEGIN;
> CREATE TABLE pg_mug (contents TEXT);
> INSERT INTO pg_mug
> VALUES('coffee'), ('sugar'), ('cream');
> COMMIT;
>
> You can even add stirring:
>
> BEGIN;
> CREATE TABLE pg_mug (contents TEXT);
> INSERT INTO pg_mug
> VALUES('coffee'), ('sugar'), ('cream');
> -- stir
> SELECT * FROM pg_mug ORDER BY random();
> COMMIT;

The mug is colored anyway, right now blue and black. Can/should we add
some syntax highlighting?

Bye

--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project

On Sun, Nov 29, 2009 at 12:10 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:

>> e.g. Outside the USA, very few people use cream (or anything
>> pretending to be cream).
>
> Uh, how come they put milk in tea only outside the USA?  As a tea
> drinker, I am confused.  ;-)

They put cream in tea inside the USA? Weird.

Anyway, don't forget this was (originally) a discussion about new mugs
for PostgreSQL Europe, where cafe au lait is definitely more common.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

Andreas 'ads' Scherbaum wrote:
> On Sat, 28 Nov 2009 17:57:38 -0500 (EST) Bruce Momjian wrote:
>
> > That highlights our multi-value INSERT too. :-) With proper wrap it
> > would be:
> >
> > BEGIN;
> > CREATE TABLE pg_mug (contents TEXT);
> > INSERT INTO pg_mug
> > VALUES('coffee'), ('sugar'), ('cream');
> > COMMIT;
> >
> > You can even add stirring:
> >
> > BEGIN;
> > CREATE TABLE pg_mug (contents TEXT);
> > INSERT INTO pg_mug
> > VALUES('coffee'), ('sugar'), ('cream');
> > -- stir
> > SELECT * FROM pg_mug ORDER BY random();
> > COMMIT;
>
> The mug is colored anyway, right now blue and black. Can/should we add
> some syntax highlighting?

Great idea --- colorful is good.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Dave Page wrote:
> On Sun, Nov 29, 2009 at 12:10 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> >> e.g. Outside the USA, very few people use cream (or anything
> >> pretending to be cream).
> >
> > Uh, how come they put milk in tea only outside the USA? ?As a tea
> > drinker, I am confused. ?;-)
>
> They put cream in tea inside the USA? Weird.

No, we don't usually put any dairy products in our tea.

> Anyway, don't forget this was (originally) a discussion about new mugs
> for PostgreSQL Europe, where cafe au lait is definitely more common.

True, but could I get a special tea mug? ;-)

INSERT INTO pg_mug VALUES('hot water', 'tea', 'sugar');

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

* Bruce Momjian:

> CREATE TABLE pg_mug (contents TEXT);
> INSERT INTO pg_mug
> VALUES('coffee'), ('sugar'), ('cream');

Shouldn't that be "ingredient" instead of "contents"?

--
Florian Weimer <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99

Bruce Momjian wrote:
> Dave Page wrote:
>
>> On Sun, Nov 29, 2009 at 12:10 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>>
>>
>>>> e.g. Outside the USA, very few people use cream (or anything
>>>> pretending to be cream).
>>>>
>>> Uh, how come they put milk in tea only outside the USA? ?As a tea
>>> drinker, I am confused. ?;-)
>>>
>> They put cream in tea inside the USA? Weird.
>>
>
> No, we don't usually put any dairy products in our tea.
>
>
>> Anyway, don't forget this was (originally) a discussion about new mugs
>> for PostgreSQL Europe, where cafe au lait is definitely more common.
>>
>
> True, but could I get a special tea mug? ;-)
>
> INSERT INTO pg_mug VALUES('hot water', 'tea', 'sugar');
>
Perhaps there should be a drink table with a one-to-many relationship to
an ingredients table...since then one could choose their own ingredients
and drink type (and you could add the assorted flavored syrups and
instant coffees in as well).

Maybe a little chalk area on one side where one could write their own
query to populate the drink table, and a referential integrity
constraint to prevent unauthorized ingredients... ;-)

A NOTIFY on insert trigger might be good as well, so one could drink as
soon as the beverage-making transaction was completed, or notify when
hot (though that would preclude ice in the ingredients)

PS..I'm mostly kidding here...

chander
>
>

--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC 27560
919-463-0999/877-258-8987
http://www.otg-nc.com

All,

Any reason why the idea of coverring the mug with a list of psql
shortcuts got shot down?

The vi mug has been very successful for thinkgeek.com ...

--Josh Berkus

2009/12/4 Josh Berkus <josh(at)agliodbs(dot)com>

> All,
>
> Any reason why the idea of coverring the mug with a list of psql
> shortcuts got shot down?
>
> The vi mug has been very successful for thinkgeek.com ...
>
> --Josh Berkus
>
> I personally couldn't find it useful. Whenever I would need to know the
shortcuts, I'd just type \?. I don't think vi has such a help system.

Thom

On Fri, 04 Dec 2009 10:05:05 -0800 Josh Berkus wrote:

> Any reason why the idea of coverring the mug with a list of psql
> shortcuts got shot down?

Why psql? Why not the SQL syntax? Why not PG-secific functions? The
latter one would be way more useful for anyone not using psql at all.

You see: there's a broad field which should be coveres, psql is just a
part of it and a small one.

> The vi mug has been very successful for thinkgeek.com ...

It's just an editor.

--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project

I'm happy to prepare the artwork for the new mug and was hoping to get it
done before I move interstate in seven days time to avoid a last-minute
rush. Can we get a decision on the text? Can someone summarize the options
so we can get to a conclusion?

Also, do we have a sample of the mug and artwork details from the
manufacturer. They usually provide details of the working area. e.g. How
close can we print to the handle and to the top and bottom of the mug?

Sorry Josh but I don't think a list of statements is appealing. As the man
said: vi is just an editor. When Tom Cruise stands on a PostgreSQL reference
guide, even HE looks tall!

On 5/12/09 7:17 AM, "Andreas 'ads' Scherbaum" <adsmail(at)wars-nicht(dot)de> wrote:

> On Fri, 04 Dec 2009 10:05:05 -0800 Josh Berkus wrote:
>
>> Any reason why the idea of coverring the mug with a list of psql
>> shortcuts got shot down?
>
> Why psql? Why not the SQL syntax? Why not PG-secific functions? The
> latter one would be way more useful for anyone not using psql at all.
>
> You see: there's a broad field which should be coveres, psql is just a
> part of it and a small one.
>
>
>> The vi mug has been very successful for thinkgeek.com ...
>
> It's just an editor.

Regards

Rob Napier

Thom Brown wrote:

>> The vi mug has been very successful for thinkgeek.com ...
>>
> I personally couldn't find it useful. Whenever I would need to know the
> shortcuts, I'd just type \?. I don't think vi has such a help system.

Try :help

--

Shane Ambler
pgSQL (at) Sheeky (dot) Biz