x using that opclass exists. The actual names of the
operators are irrelevent.
So for either rtree or GIST, all you need is to define your new datatype,
with its associated operators, and create an operator class for it with
appropriate support functions, and create indexes using that opclass.
Once a
ed purely for the convenience of the backend.
For this specific task, information_schema.columns should be pretty close
to what you need.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)-
an't be converted into additional
WHERE clauses.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ur application work on a set of views. Then you can change the
> views via "create or replace view" for switch over.
Same problem applies here.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)
On 2005-03-04, "Joel Fradkin" <[EMAIL PROTECTED]> wrote:
> Just so I don't make a newb mistake I should use timestamptz not timestamp
> where the exact moment is important?
Yes.
--
Andrew, Supernews
http://www.supernews.com - individual
2005-03-03 22:15:54-08 | 1109916954
(1 row)
Notice that the stored timestamp doesn't actually change; it is displayed
differently according to the timezone. The Unix time correctly _doesn't_
change, reflecting the fact that what we stored was the absolute time.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
s correspond to timestamp _with_ time zone.
(Why are you using timestamp without time zone anyway? For recording the
time at which an event occurred that usage is simply wrong - in fact I
can't see any situation in which a Unix epoch time can correctly be
converted to a timestamp without tim
ften
AccessExclusive, which blocks queries).
> As a test I moved the partition function call to the beginning of the
> script (before the objects were created) and it worked just fine. I
> then changed the object declarations passing in the single DB handle,
> and every now works just
r that you are checking the data only at the time of
modification, whereas CHECK constraints are declarative constraints which
are expected to be true at all times.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)
-++---+-
1 | 2005-03-21 15:05:00+00 | -08:00:00 | 2005-03-21 07:05:00
(1 row)
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)---
Now I
> need help porting the "down" the hierarchy function.
Have you looked at contrib/tablefunc's connectby() function?
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)-
IN in place of a join is
unwise (even though recent versions can sometimes plan it as though it were
a join); using UNION in place of an outer join is _very_ unwise. (In fact
UNION / INTERSECT / EXCEPT should normally be reserved for those cases
where there is simply no alternative.)
--
Andrew, S
#x27;t succeed since the b.n = 'b' condition is guaranteed to fail
> when b.* is nulled out ...
You can make it work by moving parts of the condition into the explicit
join clause:
select a.i
from t as a left join t as b on a.n='a' and b.n='b' and a.i=b.i
whe
13 matches
Mail list logo
