Hi, all
postgreSQL v7.3.3
I found EXECUTE on pl/pgsql doesn't support schema. When I specify a table
such as "public.tablename", it reported "not such a relation object". The
only SQL statement I used is "update". Don't know wether other statements
have the same problem.
Jack
-
I would imagine that since neither the size of the earth, nor the laws of mathematics
and geometry have any scheduled changes pending for their source code any time in the
near future, it's reasonable to rely on the long/lat information and extrapolate the
distances using basic planet earth dime
On Wed, 26 Mar 2003, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > On 26 Mar 2003, Greg Stark wrote:
> >> Can you show an example where the join order would affect the result set? I
> >> can't think of any.
>
> > I can think of a few somewhat degenerate cases.
>
> I don't think y
Stephan Szabo <[EMAIL PROTECTED]> writes:
> On 26 Mar 2003, Greg Stark wrote:
>> Can you show an example where the join order would affect the result set? I
>> can't think of any.
> I can think of a few somewhat degenerate cases.
I don't think you need a degenerate case. Consider
from (G le
Tomasz, Peter,
> I already know all of these things (look at thread "Formatting
> intervals" dated on 2003-03-17). I was just thinking about intervals
> idea. Keeping time inside interval is good. Keeping months inside
> interval also looks good, but keeping both of them doesn't make sense.
> It i
Tom Lane <[EMAIL PROTECTED]> writes:
> The SQL-standard way of writing this would presumably be either
>
> from G left join L on (G.SELID = L.SELID)
> left join C on (L.SELID = C.SELID and L.SELLEVEL = C.SELLEVEL)
I would think of it as this one.
> from G left join
> (
"Liang Luo" <[EMAIL PROTECTED]> writes:
> 2003-01-01 00:43:60.00-05
> Actually, the real data of second and millisecond is 59.996-05, but it shows
> 60.00. I failed to load it when I use this result in other query.
This looks like an old bug. What Postgres version are you using, and
on what plat
>
> This is the query and result:
>
> select h323_setup_time from pv_legs_new where h323_setup_time =
'2003-01-01
> 00:43:59.996-05';
>
> h323_setup_time
> ---
> 2003-01-01 00:43:60.00-05
>
> Actually, the real data of second and millisecond is 59.996-05, but it
shows
