On Thu, 30 Aug 2001, Jon Lapham wrote:
> I'm receiving the following error message:
> ERROR: Relation "log" with OID 3694127 no longer exists
>
> When running the following script (a stripped-down version of what I'm
> really doing, but it demostrates the behavior):
>
> CREATE TABLE log (logi
On Wednesday 29 August 2001 20:05, you wrote:
> hi,
> Idon't know the best way but how about a quick insert in a temp table and
> adding 1 to the inserted oid column each time the trigger will run.!
> regards
As you don't know how many users access the server concurrently and in which
order they
Hello-
I'm receiving the following error message:
ERROR: Relation "log" with OID 3694127 no longer exists
When running the following script (a stripped-down version of what I'm
really doing, but it demostrates the behavior):
CREATE TABLE log (logid int4);
CREATE TABLE data (dataid int4);
CREA
Larry Rosenman writes:
> * Peter Eisentraut <[EMAIL PROTECTED]> [010828 09:59]:
> > Larry Rosenman writes:
> >
> > > in testing CVS tip(sort of), I found that you need -lcurses with
> > > -ledit on NetBSD 1.5.1.
> > >
> > > _tputs in undefined otherwise.
> >
> > Fixed in current.
> of NetBSD?
Po
> > >For bytea, follow this rule: to escape a null character, use this:
> > >'\\0'. To escape a backslash, use this: ''.
> > >
> > >Same idea to unescape data.
> >
> > Are there other characters that need to be escaped? I suspect there are
> > more characters that need to be escaped - ctrl cha
You will find a Tutorial in the postgres documentation.
The file postgres.tar.gz located in the 'doc' subdirectory of
your source directory contains the postgres documentation in html
format.
Arne
Georgina Rodríguez wrote:
>
> Hi, I would like to start in PostgreSQL. I have never used befor
> > Does anyone else have work that they're trying to finish up before
> > we go beta?
I'm fixing and add some features to "to_char" (new to_char(interval) ).
Maybe I will finish it on this Friday.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, Po
> Does anyone else have work that they're trying to finish up before
> we go beta?
I've got some (relatively small) patches to support some ISO variations
in date/time representation.
I'm considering diving in and separating timestamp into two types,
timestamp and timestamptz supporting "with an
hi,
Idon't know the best way but how about a quick insert in a temp table and
adding 1 to the inserted oid column each time the trigger will run.!
regards
Omid
>From: Markus Wagner <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED], [EMAIL PROTECTED],
>[EMAIL PROTECTED]
>Subject: [SQL] getting the oid
Hi,
we need to control database changes within BEFORE triggers.
There is no problem with triggers called by update, but there is
a problem with triggers called by insert.
We strongly need to know the oid of a newly inserted tuple. In this case, we
use tg_newtuple of the TriggerData structure pa
On Tue, 28 Aug 2001, Lincoln Yeoh wrote:
> >For bytea, follow this rule: to escape a null character, use this:
> >'\\0'. To escape a backslash, use this: ''.
> >
> >Same idea to unescape data.
>
> Are there other characters that need to be escaped? I suspect there are
> more characters that
Hi, I would like to start in PostgreSQL. I have never used before,
where should I find something for starting, something as a tutorial.
Thank you very much for your help.
--
Georgina Rodríguez Prado
ISC ITESM
Tel. [52] (7) 3-13-22-84
MEXICO
--
Karel Zak writes:
> Hmm, I answer it oneself. A problem is in the file
> src/backend/storage/buffer/s_lock.c at line 231:
>
> #if defined(__mips__) || !defined(__sgi)
> ^
>
> this condition is true for all __mips__ or for *everythig* what is
> not __sgi__ (so i386 too)
Hmm, I answer it oneself. A problem is in the file
src/backend/storage/buffer/s_lock.c at line 231:
#if defined(__mips__) || !defined(__sgi)
^
this condition is true for all __mips__ or for *everythig* what is
not __sgi__ (so i386 too). It's the typical 'OR' problem
Patch not attached, apparently mail server rejects large files.
Patch can be found on www.formenos.org/pg/cursor.fix1.diff
Notes:
1. Incompatible changes: CURSOR is now a keyword and may not be used as an
identifier (tablename, etc). Otherwise, we get shift-reduce conflicts in
grammar.
2. Majo
Nevermind this patch then...
On Wed, 29 Aug 2001, Peter Eisentraut wrote:
> Alex Pilosov writes:
>
> > Attached patch fixes following problem: createlang.sh expects one handler
> > for each PL. If a handler function for a new PL is found in pg_languages,
> > PL won't be created. So you need to
Alex Pilosov writes:
> Attached patch fixes following problem: createlang.sh expects one handler
> for each PL. If a handler function for a new PL is found in pg_languages,
> PL won't be created. So you need to have plperl_call_handler and
> plperlu_call_handler. This patch just does that.
This
Hi,
from current CVS:
./configure --prefix=/usr/lib/postgresql \
--enable-multibyte \
--enable-locale \
--enable-nls \
--enable-recode \
--enable-unicode-conversion \
--with-openssl \
Tom Lane wrote:
>
> "Joe Conway" <[EMAIL PROTECTED]> writes:
> > ... is there a good reason that byteaout
> > octal escapes all non-printable characters?
>
> Well, AFAICS it *has to* escape nulls (zero bytes). Whether it escapes
> more stuff is a matter of taste once you accept that.
output fu
Tom Lane wrote:
[EMAIL PROTECTED]">
Vince Vielhaber <[EMAIL PROTECTED]> writes:
On Thu, 23 Aug 2001, Colin 't Hart wrote:
5. I think Bugzilla's concepts of products, components and versions fitthe way we work.I envisage that 'Postgres', 'Interfaces', 'Languages' might be prod
20 matches
Mail list logo
