I assume you are trying to create a built-in function, right?
If thats the case you may want to create an entry in pg_proc (That seems
to be missing). Search for box_add in the source code and you will get
an idea what code needs to be added where.
Rgds,
Arul Shaji
shieldy wrote:
my
* [PATCHES] Updateable cursors patch /FAST PostgreSQL/
This is incomplete, and I fear at this point has to be held over to 8.4.
It is true that my original patch post said that I need to modify the
patch to work with tidscan. Since then I have realized that this
modification is not needed
Andrew Dunstan wrote:
The CSVlog pipe is a separate pipe from the stderr pipe. Anything that
goes to stderr now will continue to go to stderr, wherever that is.
I like this scheme for a couple of reasons:
. it will include the ability to tell the real end of a message
. it will let us
Andrew Dunstan wrote:
Now that we've fixed the partial/interleaved log line issue, I have
returned to trying toi get the CSV log patch into shape. Sadly, it still
needs lots of work, even after Greg Smith and I both attacked it, so I
am now going through it with a fine tooth comb.
One
In CVS HEAD
workspace=# begin;
BEGIN
workspace=# declare cu cursor for select * from t1 for read only;
DECLARE CURSOR
workspace=# fetch cu;
a
---
1
(1 row)
workspace=# delete from t1 where current of cu;
DELETE 1
workspace=# commit;
COMMIT
Is this the intended behaviour? If so should we
Josh Berkus wrote:
Arul Shaji
Sydney, Australia.
Rgds,
Arul Shaji
Hi All,
I am now trying to implement pg_get_domaindef() function which is in the TODO
list and ran into a minor issue.
When the following command is given
CREATE DOMAIN testdomain AS text CONSTRAINT testconstraint NOT NULL;
I couldn't find the CONSTRAINT name ('testconstraint' in this case)
We are trying to develop the updateable cursors functionality into
Postgresql. I have given below details of the design and also issues we are
facing. Looking forward to the advice on how to proceed with these issues.
Rgds,
Arul Shaji
1. Introduction
--
This is a combined
On Tue, 23 Jan 2007 15:48, Joshua D. Drake wrote:
FAST PostgreSQL wrote:
We are trying to develop the updateable cursors functionality into
Postgresql. I have given below details of the design and also issues we
are facing. Looking forward to the advice on how to proceed
On Wed, 28 Feb 2007 09:48, Bruce Momjian wrote:
[Added a subejct line]
FYI, I am not going to be comfortable accepting a final patch that
contains this email signature:
This is an email from Fujitsu Australia Software Technology Pty Ltd, ABN
27 003 693 481. It is confidential to
On Thu, 1 Mar 2007 04:28, Bruce Momjian wrote:
I have added this to the developer's FAQ to clarify the situtation of
posting a patch:
liPostgreSQL is licensed under a BSD license. By posting a patch
to the public PostgreSQL mailling lists, you are giving the PostgreSQL
Global
On Fri, 2 Mar 2007 01:20, Simon Riggs wrote:
On Thu, 2007-03-01 at 15:17 +1100, FAST PostgreSQL wrote:
Hi Simon,
We are happy to provide that. If and when it comes to the final patch
being accepted, we can send a copyright waiver mail which will put our
source code contribution under
12 matches
Mail list logo
