From: | Jeff Eckermann <jeff_eckermann(at)yahoo(dot)com> |
---|---|
To: | "tvis" <tovises(at)freemail(dot)hu>, pgsql-novice(at)postgresql(dot)org |
Subject: | Re: records chaining |
Date: | 2005-04-19 13:59:19 |
Message-ID: | 20050419135919.84810.qmail@web20828.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
This message, along with your previous one, suggests
that you are trying to limit the size of your tables.
Is there any good reason for this? How many records
do you expect to have? What hardware will you be
running on?
--- tvis <tovises(at)freemail(dot)hu> wrote:
> I need record changing history. Of course I need to
> keep old records, and some how point to it for show
> changes. First of my idea is to make a single column
> in every record pointing to his "parent" but after I
> started thinking how SQL can handle it. Whats your
> opinion, is it possible to write a recursive SELECT
> to get all records back to that whats parent
> reference has no reference (NULL)? At this moment I
> would be happy to know that is it possible - I'm
> only planning and migrating an old database, the
> coding seem to be "far" away.
> Thanks in advance
> Gbor Rzsa
>
>
__________________________________
Do you Yahoo!?
Plan great trips with Yahoo! Travel: Now over 17,000 guides!
http://travel.yahoo.com/p-travelguide
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-04-19 14:46:33 | Re: Postgresql works too slow |
Previous Message | Kevin Crenshaw | 2005-04-19 13:49:44 | Are there any known issues with running MSDE and Postgresql 8.0 on the same machine? |