Re: [BUGS] Strangeness/bug when working with my own datatype in PostgreSQL

2001-02-24 Thread Tom Lane
=?KOI8-R?Q?=F3=CF=CC=CF=C4=CF=D7=CE=C9=CB=CF=D7_=EB=CF=CE=D3=D4=C1?= =?KOI8-R?Q?=CE=D4=C9=CE?= <[EMAIL PROTECTED]> writes: > When I insert a new row into this table without providing a value for the > "i1" column, I get a value of "45" in it. Seems odd to me too; it should default to NULL if no

[BUGS] Strangeness/bug when working with my own datatype in PostgreSQL

2001-02-24 Thread Солодовников Константин
Good time of day! I've got some strangeness/bug when working with my own datatype in PostgreSQL. Here's a short description of the sitiation: I've developed a 1-byte integer datatype (let's call it "int1"). The input and output functions for this datatype I wrote myself. Everything works just f

Re: Lock Detection (was: [BUGS] pg_dump failing on LinuxPPC)

2001-02-24 Thread Tom Lane
Stu Coates <[EMAIL PROTECTED]> writes: > I come from an Oracle background where I can lock an item of data by > performing a "SELECT FOR UPDATE" on the row. This is also implemented > in PostgreSQL. A quite useful feature Oracle does have is the ability > to add a "NOWAIT" clause to the end of t

Re: [BUGS] Sequence of characters not supported by psql/pg_dump

2001-02-24 Thread Tatsuo Ishii
> Le jeu, 11 jan 2001, Tatsuo Ishii a écrit : > > > I use PostgreSQL 7.0.2 on linux. > > > The base was set with initdb -E UNICODE. > > > > > > I have many Strings with accents (french language). > > > Some of them aren't supported by queries or pg_dump: > > > > > > WORKING EXAMPLE: > >