Marc Boucher <[EMAIL PROTECTED]> writes:
> CREATE OR REPLACE RULE albed_updalb3_rl AS
>ON UPDATE TO album WHERE new.pls_id != old.pls_id
> DO
>UPDATE album_edit SET pls_id=new.pls_id WHERE alb_id=new.id;
> It works until new.pls_id or old.pls_id is null. The rule is still called
> (base
Kris Jurka <[EMAIL PROTECTED]> writes:
> On Fri, 22 Oct 2004, Tom Lane wrote:
>> You are confusing the syntax for a typed literal with part of the AT
>> TIME ZONE construct.
> Could you explain what the difference is between a typed literal
> "int '11'" and a cast(ed) literal "'11'::int" to me the
On Fri, 22 Oct 2004, Tom Lane wrote:
> You are confusing the syntax for a typed literal with part of the AT
> TIME ZONE construct.
Could you explain what the difference is between a typed literal
"int '11'" and a cast(ed) literal "'11'::int" to me they seem like the
same thing.
Kris Jurka
-
This is a resent. Wrong email account the first time.
---
I'm using PostgreSQL 7.3.4.
I've set up a series of rules and triggers to complete an intermediate
table with similar informations from another table. This ensures better
performance over a solution with views.
Intermediate table:
Tab
Kris Jurka <[EMAIL PROTECTED]> writes:
> AT TIME ZONE INTERVAL $1 doesn't seem to be supported in prepared
> statements.
Try
AT TIME ZONE $1
or possibly
AT TIME ZONE $1::interval
You are confusing the syntax for a typed literal with part of the AT
TIME ZONE construct.
AT TIME ZONE INTERVAL $1 doesn't seem to be supported in prepared
statements.
This works:
SELECT now() AT TIME ZONE INTERVAL '-08:00';
This doesn't:
PREPARE mys(text) AS SELECT now() AT TIME ZONE INTERVAL $1;
ERROR: syntax error at or near "$1" at character 57
These work:
PREPARE mys(inter
Clean build of pgsql 7.4.5 on HPUX B.11.23 on ia64 with
--enable-thread-safety fails ... :(
$uname -a
HP-UX ... B.11.23 U ia64 0144848471 unlimited-user license
$cd postgresql-7.4.5
$./configure --enable-thread-safety --without-readline --without-zlib
...
checking pthread.h usability... yes
ch
"Ed L." <[EMAIL PROTECTED]> writes:
> Noticed this when I had a typo on the configure command line. The configure
> script does not catch the following bogus option:
> --enable-bogosity
Complain to the Autoconf project. They strenuously insist this is not a
bug, and have done so for many
Noticed this when I had a typo on the configure command line. The configure
script does not catch the following bogus option:
--enable-bogosity
That might seem like no biggie, but it also doesn't seem to notice this
error:
--enable-thread-safeyt (notice the mispelling)
Makes
> > Olá !
> >
> > Preciso instalar o PostgreSql beta 8 para Windows em um computador
> > Windows 2000 server. Este computador é um controlador de
> comínio e não
> > possui conta de usuário local. Como faço para instalar sem
> um usuário administrador local??
> >
> > Obrigado pela atenção.
"Rodrigo Ferraz" <[EMAIL PROTECTED]> writes:
> Olá !
>
> Preciso instalar o PostgreSql beta 8 para Windows em um computador Windows 2000
> server. Este computador é um controlador de comínio e não possui conta de
> usuário local. Como faço para instalar sem um usuário administrador local??
>
>
11 matches
Mail list logo
