> Long Description PostgreSQL has mechanism for commenting databases.
> Database comments can by read by obj_description(oid), psql \l+ command
> use it. Database comments should be global, but they are not, when we do
> \l+ on one database, and then on other, results will be different. I
> conside
> Long Description
> I try to create language plpgsql for db "template1" on solaris 9 but don't work.
> It's seems that all other work, but i' don't sure.
> Below i write the response of shell (bash).
>
> Sample Code
> bash-2.05$ createlang plpgsql template1
> ERROR: Load of file /usr/local/pgsql
Hi,
I am using postgresql 7.2.1.
How do i cast an integer value to boolean? I did try the below sequence of
SQLs and was little bit confused, by the way it behaves. It casts the
integer value to boolean in one case but not ever again.
bhuvan=> SELECT count(*)::int::boolean from my_table;
ERROR:
hi,
Hope you might have came accross this problem earlier. it exists in
7.1.x and 7.2 as well.
while creating a table with a column of type 'serial', well a sequence
has been created and the default value of that field is set to nextval
of that sequence, fine. But while dropping that table, why
On Mar 11, Stephan Szabo wrote:
>
> On Mon, 11 Mar 2002, Bhuvan A wrote:
>
> >
> >
> > On Mar 10, Stephan Szabo wrote:
> >
> > > On Mon, 11 Mar 2002, Bhuvan A wrote:
> > >
> > > > here i have a problem in comparing null
On Mar 10, Stephan Szabo wrote:
> On Mon, 11 Mar 2002, Bhuvan A wrote:
>
> > here i have a problem in comparing null values in plpgsql. this exist
> > in 7.1.x and 7.2 as well.
> >
> > the condition != fails in plpgsql.
> > consider this function is tr
hi,
here i have a problem in comparing null values in plpgsql. this exist
in 7.1.x and 7.2 as well.
the condition != fails in plpgsql.
consider this function is triggered on every updation on a table.
create function ftest()
returns opaque as 'declare
begin
if new.comp_code != ol
