Re: PG Admin

From: Alban Hertroys <alban(at)magproductions(dot)nl>
To: Bob Pawley <rjpawley(at)shaw(dot)ca>
Cc: Steve Atkins <steve(at)blighty(dot)com>, PgSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: PG Admin
Date: 2006-12-05 09:31:43
Message-ID: 45753C7F.1020106@magproductions.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bob Pawley wrote:
>> I'm sure that PG Admin just generates the numbers in the GUI as it
>> displays them (as they're meaningless as persistent data).

> Perhaps - but they aren't necessarily meaningless as pure information.

Can't you just do the same - generate the numbers within your
application - and only store them once this "construction phase" ends?

It seems weird to keep some arbitraty numbering scheme in the database.

What does it signify in that phase? Does order matter at all - or is
that what it's supposed to be?

You could also use a mixed solution:
- use a sequence during the construction phase to order by,
- generate the "real" numbering in your client application based on that
order,
- store the generated numbers instead of the sequence values once the
construction phase is finished.

PS. please don't top post, I had to reconstruct your message to let it
make sense.
--
Alban Hertroys
alban(at)magproductions(dot)nl

magproductions b.v.

T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede

// Integrate Your World //

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Anton 2006-12-05 09:38:54 Re: JOIN work somehow strange on simple query
Previous Message Anton 2006-12-05 09:05:35 JOIN work somehow strange on simple query