What do folks think?
Take care,
Bill
Hello Bill,
The community have been waiting for packages for a long time. I don't
believe you did it!!!
IMHO most applications do not fully benefit from the power of PostgreSQL
because transactions are performed at application lever
Do we still need code to warn during VACUUM when you get near to OID
wraparound? I know Tom has handled XID wraparound and has OID usage
decreased.
I have a patch to warn about OID wraparound but don't know if it is
still desired.
--
Bruce Momjian|
While looking to implement the ODBC replace() function (replace occurences
of $2 in $1 by $3), I found that it could be expressed as:
CREATE FUNCTION replace(text, text, text) RETURNS text AS '
select
case when position($2 in $1) = 0 or char_length($2) = 0
then $1
Thomas Lockhart writes:
Oh yeah. We don't have a date_part(units, time) function defined, so it
is getting converted to interval (which in other contexts *does* have
some usefulness as a time equivalent).
You're going to have an extremely hard time convincing me of that.
We could fairly
Bruce Momjian [EMAIL PROTECTED] writes:
Do we still need code to warn during VACUUM when you get near to OID
wraparound?
I don't think so.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
Bill Studenmund [EMAIL PROTECTED] writes:
... operators and types in
packages are in the same name space as are types and operators not in
packages.
For functions and aggregates, things are a little more complicated. First
off, there is a package called standard which contains all types,
Looks like Monday is our next beta target date. My mailbox is empty of
outstanding patches except for an ecpg one I will apply tomorrow unless
someone objects to it.
There are some patches still being worked on, but there always will be.
--
Bruce Momjian|
BTW, the postgres docs web pages says there is no limitation on row
size. Someone should probably update that with the info given in the
last few emails and probably integrate it in the regular doco as well.
Although the field length is limited to 1GB, is there a row size limit?
I don't know
Bill Studenmund [EMAIL PROTECTED] writes:
In 7.1 I was able to get this (I thought) with
date_part(''epoch'', timestamp ''now'') . That doesn't seem to work for me
in last week's -current.
Indeed: in 7.1 I can do
test71=# select date_part('epoch', timestamp 'now');
date_part
Tom Lane writes:
Peter Eisentraut [EMAIL PROTECTED] writes:
I had figured that time would be cast to timestamp.
How would you do that? With no date available, you're short all the
high-order bits ...
For the purpose of extracting the fields that time does provide, namely
hour, minute,
Bill Studenmund writes:
So what are packages? In Oracle, they are a feature which helps developers
make stored procedures and functions.
I think you have restricted yourself too much to functions and procedures.
A package could/should also be able to contain views, tables, and such.
They
Bruce Momjian writes:
OK, new FAQ code is:
$sql = SELECT nextval('person_id_seq');
$newSerialID = ($conn-selectrow_array($sql))[0];
INSERT INTO person (id, name) VALUES ($newSerialID, 'Blaise Pascal');
$res = $dbh-do($sql);
This code is still incorrect for any
Bruce Momjian writes:
OK, let's assume we have pre-forked backends that do the accept(). One
enhancement would be for the child to connect to the last requested
database. If the accept() user wants the same database, it is already
connected, or at least its cache is loaded. If they
Peter Eisentraut [EMAIL PROTECTED] writes:
I was wondering whether, as a future project, we could make this more
convenient by parsing the body of the function with the binding of the
function already in effect.
Seems like a simple rearrangement of the code. First insert the pg_proc
entry,
ASCII SQL_ASCII
UTF-8 UNICODE UTF_8
MULE-INTERNAL MULE_INTERNAL
ISO-8859-1 LATIN1 ISO_8859_1
ISO-8859-2 LATIN2 ISO_8859_2
ISO-8859-3 LATIN3
15 matches
Mail list logo
