| From: | mixo <mixo(at)beth(dot)uniforum(dot)org(dot)za> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: age |
| Date: | 2002-07-16 12:41:07 |
| Message-ID: | 3D341463.8090508@beth.uniforum.org.za |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
That would solve the problem completely if I did not have a situation
where "status" (the other column) was not NULL - the reason for it
being that way is that it was added when the table was modified and
a default value was not set. But, for now I am going to check if the
"locktime" is NULL before proceeding.
Sam Liddicott wrote:
>Yeah, have another column for storing the age, or have another column to
>store whether or not it is locked and don't use NULL in locktime.
>
>You can't retreive data that you aren't storing.
>
>Sam
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2002-07-16 12:42:03 | Re: PostgreSQL in mission-critical system |
| Previous Message | Bruno Wolff III | 2002-07-16 11:32:35 | Re: Question: merit / feasibility of compressing frontend |