From: | Dennis Gearon <gearond(at)cvc(dot)net> |
---|---|
To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [SQL] rewriting values with before trigger |
Date: | 2003-04-24 20:35:40 |
Message-ID: | 3EA84A9C.1040901@cvc.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
I **LIKE** your kind of thinking :-)
Don't mess up the data.
Don't mess up the schema.
It hurts or causes LOTS of labor later on.
Robert Treat wrote:
> On Thu, 2003-04-24 at 15:35, Dennis Gearon wrote:
>
>>Well,
>> does ''::INT do anything valuable?
>
>
> not in 7.3+, and given my original problem involves timestamps, not in
> 7.2 either.
>
>
>> change column to a string, convert to INTS on the way out, STRINGS on the way in?
>> use an external language to make transitions.
>>
>
>
> yeah, I've thought of some other crazy ways to get around this, but the
> problem is due to a bug in the application side. I was hoping I could
> write a quick hack (like adding a rule/trigger) to get around this until
> the app was fixed, but I'm not going to make my side a kludge when it
> isn't one now.
>
>
> Robert Treat
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dennis Gearon | 2003-04-24 20:36:58 | Re: ODBC & Access [Try 2] |
Previous Message | scott.marlowe | 2003-04-24 20:21:53 | Re: SERIAL type fields |
From | Date | Subject | |
---|---|---|---|
Next Message | nolan | 2003-04-24 21:18:05 | Re: [SQL] rewriting values with before trigger |
Previous Message | Robert Treat | 2003-04-24 19:49:05 | Re: [SQL] rewriting values with before trigger |