Hi
I notice that string function textpos() doesn't exist in
postgreSQL 7.0. I have some
plpgsql functions written for 6.5.2 that use textpos() and
when I tried to use them
in postgreSQL 7.0 I'v got error. Should I compile postgreSQL
7.0 with more options
than -enable locale ?!!?
Thanks for
"Alexander H. Iliev" <[EMAIL PROTECTED]> writes:
> test=# select * from a natural inner join b natural inner join c;
> pqReadData() -- backend closed the channel unexpectedly.
Yup, I see it too. I had fixed some problems in SQL join syntax
since 7.0 release, but evidently not this one :-(. Will
> > oh, btw this select refused to use an SQL natural join among the 3
> > relations - the server gives up and disconnects without warning.
>
> That sounds like a garden-variety bug. I'd be willing to look at it
> if I had a complete example to follow, but I don't want to try to
> reverse-engine
"Alexander H. Iliev" <[EMAIL PROTECTED]> writes:
> does anyone have a clue what this diagnostic from psql (v 7.0) means:
> ERROR: aggregate function in qual must be argument of boolean operator
Aggregates and GROUP BY in views have a lot of restrictions at the
moment, and this is one of them: th
Hi all,
does anyone have a clue what this diagnostic from psql (v 7.0) means:
ERROR: aggregate function in qual must be argument of boolean operator
I got it from this query:
SELECT *
FROM last_payment NATURAL INNER JOIN admin_info
WHERE date_part ('month', age(last_payment.date, timestamp 'no
mikeo wrote:
>
> hi,
> in oracle you would use these two cursors to determine who was connected and
> what they were doing.
>
> select distinct s.sid sid, s.serial# serial, s.status status, osuser, spid ,
> count(o.sid) counter, s.username username, s.program program, sql_address
> from v$sessio
Kyle Bateman wrote:
Hi Jan:
But when I create it with "create constraint trigger" as shown next,
the trigger doesn't seem to be invoked. It says it is created, but
it allows data to pass that would not be allowed with the "create trigger."
So I'm assuming I'm doing something wrong.
create const
Wallingford, Ted writes:
> I am using 6.3 in this case.
I'm sorry but that is pre-historic era around here and no one really
remembers what the problems might have been back then (other than that
they were surely plenty). Upgrading might be your best bet on all fronts.
--
Peter Eisentraut
I'm not entirely sure what the correct term for this would be, but
I'll just call it an inhertiance heirarchy for lack of a more
correct name.
Anyway, I'd like some pointers on modeling a heirarchical structure
where a given "parent" row can have multiple "children" rows, and
each "child" has eit
thanks for the hlep guys..
for those that are curious, the distinct is tehr cause it's
someone elses code that i'm workig on .. :) have to kick
out the bug's//
jeff
On Tue, 30 May 2000, Matthias Urlichs wrote:
> Hi,
>
> Jeff MacDonald:
> > gid is unique.. it's a serial..
> >
> Then there is
hi,
in oracle you would use these two cursors to determine who was connected and
what they were doing.
select distinct s.sid sid, s.serial# serial, s.status status, osuser, spid ,
count(o.sid) counter, s.username username, s.program program, sql_address
from v$session s, v$open_cursor o, v$proc
> > Does anyone know why when I am in a particular DB as user postgres and
use
> > the following statement, why I get this error?"
> >
> > This is the statement;
> > SELECT * FROM some_file where ID = 1;
> >
>
> --
--
> > Erro
What is the definition of the table 'some_table'??
Regards,
Ed Loehr
Rick Parker wrote:
>
> Does anyone know why when I am in a particular DB as user postgres and use
> the following statement, why I get this error?"
>
> This is the statement;
> SELECT * FROM some_file where ID = 1;
>
> -
Does anyone know why when I am in a particular DB as user postgres and use
the following statement, why I get this error?"
This is the statement;
SELECT * FROM some_file where ID = 1;
Error: ERROR: attribute 'id' not
Rostislav Opocensky <[EMAIL PROTECTED]> writes:
> On Tue, 30 May 2000, Tom Lane wrote:
>> The problem here is that the optimizer will only consider an indexscan
>> for a clause that looks like index_key OP constant. It doesn't think
> I'll consider having my index function return a `date'. Stil
Hi All,
I am trying to enable my web site to create views in a database owned by a
user called ddirpts. Now, the web server runs as nobody, and nobody has a
user and database set up in Postgres.. But the problem is, whenever I have a
cgi program issue a create view query on the ddirpts database,
On Tue, 30 May 2000, Tom Lane wrote:
> The problem here is that the optimizer will only consider an indexscan
> for a clause that looks like index_key OP constant. It doesn't think
> that trunc_to_day('28.5.2000') is a constant, because you haven't told
> it that it can pre-evaluate that functio
Hi Jeff!
I think you need a solution, and not explains...
Tom, and the others told the truth. You missed this query.
> gid is unique.. it's a serial..
I give you two ways:
1) gid __realy__ unique -> DISTINCT is unnecessary.
SELECT gid FROM members -- ... etc
2) gid not unique -> DISTINCT
18 matches
Mail list logo
