After the CREATE statement I would simply put:
INSERT INTO emp VALUES ('Bill', 4200, 45, '(2,1)');
What that accomplishes is making it so the user can simply copy and
paste the entire section and run it in pg_admin. Then, the user can
start fiddling with it as he wants to.
I know this sounds terribly simple, but simplicity is good,
particularly when you're climbing a steep learning curve. And there
is certainly, unequivocally, no harm in simplicity.
Thanks,
John
On Jul 24, 2010, at 2:21 PM, Peter Eisentraut wrote:
> On fre, 2010-07-23 at 12:02 +0200, John Gage wrote:
>> In this section, you create the table for the example, but you do
>> not
>> populate it, although the example select statements are against the
>> phantom population that has not been inserted.
>>
>> I suggest strongly including the minimal code necessary to populate
>> the table, so that the user doesn't have to populate it himself.
>> Call
>> me lazy, but I did go into pgAdmin and insert values after creating
>> a
>> primary key.
>
> Could you send a patch, or a list of the statements that need to be
> inserted?
>
>
> --
> Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs
