Nope, neigher PyGreSQL nor ""PGSQL"" are products of
Pgsql.com (aka PostgreSQL Inc)On Mon, 9 Oct 2000, Vince Vielhaber wrote:
On Mon, 9 Oct 2000, Bruce Momjian wrote:
I need to know how this is different than our current python interface,
PyGreSQL.
Is this a product of pgsql.com?
The Hermit Hacker wrote:
On Mon, 9 Oct 2000, Bruce Momjian wrote:
Ya, but in one email, you appear to agree with me ... then Tom posts a
good point and you jump over to that side ... at least pick a side? :) I
too wish to see it implemented, I just don't want to have to double my
disk
-Wmissing-prototypes -Wmissing-declarations -o pg_dump pg_dump.o common.o
pg_backup_archiver.o pg_backup_db.o pg_backup_custom.o pg_backup_files.o
pg_backup_null.o pg_backup_tar.o -L../../..
/src/interfaces/libpq -lpq -lz -lcrypt -lnsl -ldl -lm -lreadline -lncurses
-lz
On Sun, Oct 08, 2000 at 01:37:45PM -0400, Bruce Momjian wrote:
But perhaps it is ecpg's fault for including "elog.h".
IMHO these defines should never leave the database kernel.
...
Yes, leaking into user programs is a bad practice. Is there a
solution/patch for that?
Hmm, I haven't
The Hermit Hacker writes:
Announce: Release of PyGreSQL version 3.0
When is 7.1 being locked down? I may be releasing 3.1 with a few small
fixes and changes very soon.
you should be safe until mid-december or so ... as PyGreSQL doesn't affect
the build of PostgreSQL in anyway
Bruce Momjian writes:
I need to know how this is different than our current python interface,
PyGreSQL.
PgSQL is a package of two (2) modules that provide a Python DB-API 2.0
compliant interface to PostgreSQL databases.
DB-API is the standard database interface for Python. Kind of like
Hiroshi Inoue writes:
For example the following line
CFLAGS+= -DFRONTEND -I$(srcdir)
in makefiles doesn't work currently.
I found the recent change in Makefile.global.in.
ifeq ($(GCC), yes)
override CFLAGS += -Wall -Wmissing-prototypes -Wmissing-declarations
endif
Seems like a
Bruce Momjian wrote:
As promised, the press release is at:
http://www.greatbridge.com/news/p_101020001.html
Wow. Nice. The combined qualifications of the six steering committee
members are staggering.
Me, I'm just a lowly broadcast engineer with ten years experience and a
measly
Philip, where did we leave this?
If anyone is interested in being sent the current sources for the new
pg_dump pg_restore, please let me know.
The utilities now seem to work, but need testing.
The basic idea is to use pg_dump to dump an *entire* database, and then use
pg_restore to
If anyone was following my request to have a large object api for TOAST,
this is of interest.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be
At 21:01 10/10/00 -0400, Bruce Momjian wrote:
Philip, where did we leave this?
In CVS. ;-).
The longer answer is that it's been in CVS for a while, and I have a
version for 7.0.2 which I have also been using for a while. Various people
have tested it, but not as many or as much as I would like
I am tempted to apply this. This is the second person who asked for
binding to a single port. The patch looks quite complete, with doc
changes. It appears to be a thorough job.
Any objections?
Your name : David MacKenzie
Your email address: [EMAIL PROTECTED]
On Tue, 10 Oct 2000, The Hermit Hacker wrote:
On Wed, 11 Oct 2000, Christopher Sawtell wrote:
On Wed, 11 Oct 2000, [EMAIL PROTECTED] wrote:
The project name on SourceForge is "Python Interface to PostgreSQL".
How about PIPgSQL or piPgSQL?
Perhaps Pi2PgSQL, or PySQL_ba
Bruce Momjian wrote:
I am tempted to apply this. This is the second person who asked for
binding to a single port. The patch looks quite complete, with doc
changes. It appears to be a thorough job.
A cursory inspection makes it look like the socket file can be placed
_anywhere_ -- even
Peter Eisentraut wrote:
Billy G. Allie writes:
PgSQL v1.0 has been released. This is the first public release of PgSQL.
It is available at http://sourceforge.net/projects/pgsql.
Sounds interesting, but isn't "pgsql" an extremely unfortunate choice of
name, given that it's already used
On Tue, 10 Oct 2000, Bruce Momjian wrote:
I am tempted to apply this. This is the second person who asked for
binding to a single port. The patch looks quite complete, with doc
changes. It appears to be a thorough job.
Any objections?
From a quick read of his "description of problem",
Tom Lane wrote:
"Billy G. Allie" [EMAIL PROTECTED] writes:
Peter Eisentraut wrote:
Sounds interesting, but isn't "pgsql" an extremely unfortunate choice of
name, given that it's already used as an abbreviation for "PostgreSQL"?
PgSQL is the name of the module you import in Python to
At 01:02 PM 10/10/00 -0400, Tom Lane wrote:
Bottom line is we're not sure what to do now. Opinions from the
floor, anyone?
Yeah, quit worrying and work your collective butts off on 7.1 and 7.2 :)
Seriously...the core group is obviously committed to PG, and appear to
be folks of integrity.
At times I need to call PQendcopy, how to I determine that it won't
block me waiting for output from the backend?
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a jar on my desk."
Hello,
I have quite strange behavior of the following SQL:
insert into address (cid,email) select distinct '49'::int,member.email from
member imit 1 ;
It should insert just 1 record.
But it insert all recodrs which will be selected by subselect...
What's wrong with this SQL? Or this is a bug?
20 matches
Mail list logo
