db=# CREATE FUNCTION schma.tbl_ins_upd() RETURNS TRIGGER AS 'BEGIN
EXECUTE public.mc_init();
EXECUTE public.mc_delete(''mc_key'');
RETURN NEW;
END;' LANGUAGE 'plpgsql';
db=# CREATE FUNCTION schma.tbl_del() RETURNS TRIGGER AS 'BEGIN
EXECUTE public.mc_init();
Tom Lane wrote:
Weiping He <[EMAIL PROTECTED]> writes:
I've put the config.log on:
http://www.pgsqldb.org/config.log
configure:10847: cc -Ae -c +O2 -D_XOPEN_SOURCE_EXTENDED conftest.c >&5
(Bundled) cc: warning 480: The -A option is available only with the C/ANSI C prod
Tom Lane wrote:
Weiping He <[EMAIL PROTECTED]> writes:
Check the config.log, it said that the configure script can't find the
argument types
fo 'accept()'.
Could you show us the relevant section of config.log, instead of giving
a summary with no details? I'
When trying to build the CVS source on a HP-UX 11.00 box:
HP-UX hpux B.11.00 A 9000/800
We got the configure error:
checking types of arguments for accept()... configure: error: could not
determine argument types
Check the config.log, it said that the configure script can't find the
argument t
Hi,
just try to compile newly updated 7.4-devl version on a AIX 4.4.3 box,
(just checkouted about 24 hours)
but seems got problem:
8<---
make[3]: Entering directory
`/home/
Tom Lane wrote:
I think Bruce already fixed this. How old is your CVS pull?
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
upgraded this morning, around 2003-07-04 09:29:00 CST or 2003
Hi,
I'm trying to compile pgsql-7.4devl on Solaris8, but got the error
below:
8<-
numeric.c: In function `PGTYPESnumeric_cmp':
numeric.c:1308: `INT_MAX' undeclared (first use in this fu
Tom Lane wrote:
Weiping He <[EMAIL PROTECTED]> writes:
because the data type (UUID) is a struct,
and the uuid_eq() function accept two pointer to the value of struct uuid,
if make it IMMUTABLE, postgresql would think it should not try to run
the function, but return the cached value i
Tom Lane wrote:
Weiping He <[EMAIL PROTECTED]> writes:
we found the problem:
We used IMMUTABLE modifier in our CREATE FUNCTION definition,
though it's correct for our function to return same value if input the
same *data*,
but our data are passed by reference, not by value, so, so
he problem.
So, it seems to make it clear in docs would be a good help to function
writers,
would commit a documentation patch later if necessary.
Thank you!
Regards
Laser
Tom Lane wrote:
Weiping He <[EMAIL PROTECTED]> writes:
the situation trun worse: now the explain shows the
Tom Lane wrote:
"Wang Mike" <[EMAIL PROTECTED]> writes:
but this query: select * from test_uuid where id =
'df2b10aa-a31d-11d7-9867-0050babb6029'::uuid dosn't use index
QUERY PLAN
---
Seq Scan on te
Hi, all
I've found a problem in pl/pgsql: the variable declared can't be the
same name of table's column name, here is a example:
---8<
drop table userdata;
create table userdata (
userid text,
txnid text,
passwd text
>
> en_GB would be a "British English" translation. I don't think this is
> what you wanted to do.
>
cn_GB, sorry. :-D
Regards
Laser Henry
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "
Peter Eisentraut wrote:
> Tatsuo Ishii writes:
>
> > I have a plan to translate 7.1 docs into Japanases
>
> Btw...
>
> One thing I am thinking about doing for the 7.2 cycle is set up the
> doc/src/ directory in a way to keep translations in tree. It would
> probably look something like:
>
> doc/
>
> > appropriate. There are several encodings for Chinese including
> > GB(EUC-CN), Big5, EUC-TW. At least we should be able to distinguish
> > them. What about "chinese(GB)" or whatever?
>
> Renamed to chinese-gb.
>
I think chinese-gb is ok, thanks!
Regards
Laser
Hi all:
The attachement is the Chinese (GB) patch for PgAccess, don't know
if it's correct to post here.
It's simple to do the translation, And I've test in 7.0.2 & current CVS,
seems pretty good.
If anyone want this little thing, I'll very happy.
use it is very simple, just gunzip it and copy
I'm using cvs-current, and testing those
build-in function
according to the docs.
but it seems the "lpad",
"rpad" don't work,
when I type:
select lpad('laser', 4, 'a');
in psql, the result is still
'laser', the same with 'rpad',
Is it a bug or I'm mis-understaning the lpad and/or rpad
func
-Original Message-
~{7"<~HK~}: xuyifeng <[EMAIL PROTECTED]>
~{JU<~HK~}: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
~{HUFZ~}: 2000~{Dj~}11~{TB~}28~{HU~} 16:22
~{VwLb~}: [HACKERS] beta testing version
>Hi,
>
> how long is PG7.1 already in beta testing? can it be released before
Christmas day
18 matches
Mail list logo
