| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Richards <miker(at)scifair(dot)acadiau(dot)ca> |
| Cc: | pgsql-sql(at)postgreSQL(dot)org |
| Subject: | Re: [SQL] Array Madness |
| Date: | 1999-09-14 15:45:54 |
| Message-ID: | 16624.937323954@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Michael Richards <miker(at)scifair(dot)acadiau(dot)ca> writes:
> On Tue, 14 Sep 1999, Tom Lane wrote:
>> In the meantime, perhaps it would be better for ExecEvalArrayRef() to
>> raise an error if the assign source is null, rather than dropping the
>> whole contents of the array. Comments?
> This sounds like a hack that avoids the real issue...
Well, of course it's not a solution to the real issue, but it seemed
like it might prevent someone from accidentally losing data until
we get around to providing a real solution. (Which could be a long
time; there's a lot of things on the TODO list...)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stéphane FILLON | 1999-09-14 16:50:09 | Permission problem with COPY FROM |
| Previous Message | Michael Richards | 1999-09-14 15:42:53 | Re: [SQL] Array Madness |