| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
|---|---|
| To: | bhirt(at)mobygames(dot)com | 
| Cc: | pgsql-hackers(at)postgreSQL(dot)org, Brian Hirt <bhirt(at)loopy(dot)berkhirt(dot)com> | 
| Subject: | Re: [HACKERS] union in an in clause and timestamp | 
| Date: | 2000-02-03 01:17:17 | 
| Message-ID: | 24321.949540637@sss.pgh.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Brian Hirt <bhirt(at)mobygames(dot)com> writes:
> Okay, I'm running into two things that I would expect to work. 
> basement=> select 'hello' where 1 in (select 2 union select 1);
> ERROR:  parser: parse error at or near "union"
UNION isn't currently supported in sub-selects.  Hopefully we can make
it work after the long-threatened querytree redesign.  But right now,
the union code is so crufty that no one wants to touch it...
> And then, I find that I cannot create an index on a 
> timestamp column;
> basement=> create index ttt on ts(t); 
> ERROR:  Can't find a default operator class for type 1296.
For the moment, use one of the other time-related types instead.
After the dust settles from Thomas' upcoming consolidation of the
date/time datatypes, I expect everything that remains will have a
complete set of operators and index support.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Bitmead | 2000-02-03 01:30:26 | Proposed Changes to PostgreSQL | 
| Previous Message | Tom Lane | 2000-02-03 01:00:02 | Re: [HACKERS] SELECT FOR UPDATE leaks relation refcounts |