I have added this to the TODO list:
* Add OR REPLACE clauses to non-FUNCTION object creation
I think there are clearly some other objects that need OR REPLACE. Not
sure which ones yet.
---
> Dear all,
>
> Would
> > I'm working on making some changes to the top level configure.in and m4
> > has now been running for 17 minutes on a 1.4G tbird. Am I missing
> > something or is this know to take forever?
>
> For me, the autoconf run is "instantaneous". Make sure you're using
> Autoconf 2.13, and you don't
Reply.
> On Sat, Oct 20, 2001 at 05:24:39PM +0200, Ron de Jong wrote:
> > Not even close!
> >
>
> Oh? What's it missing? the \dt display in psql has all the information
> in your mythical table versionbelow, just organized a little differently,
> doesn't it?
>
> Particularly on the hackers list,
> > > Alternatively, could someone implement CREATE OR DROP VIEW / TRIGGER? These
> > > features are needed for pgAdmin II (we could also provide a patch for
> > > PhpPgAdmin). If this cannot be implemented in PostgreSQL, we will go for
> > > pseudo-modification solutions (which is definitely not
On Tue, 23 Oct 2001, Thomas Lockhart wrote:
> (I've been following the thread, at least casually ;)
>
> > intent-based. The '+' operator means I want these two things added
> > together. I don't care so much what types are involved, I want adding to
> > happen. That's a difference of intent. And
Hi All,
In the LOCK TABLE docs it documents the SELECT...FOR UPDATE as follows:
ROW SHARE MODE
Note: Automatically acquired by SELECT...FOR UPDATE. While it is a shared
lock, may be upgraded later to a ROW EXCLUSIVE lock.
Conflicts with EXCLUSIVE and ACCESS EXCLUSIVE lock modes.
How
> Dear all,
>
> Would it be possible to implement CREATE OR REPLACE VIEW / TRIGGER in
> PostgreSQL 7.2?
>
> Alternatively, could someone implement CREATE OR DROP VIEW / TRIGGER? These
> features are needed for pgAdmin II (we could also provide a patch for
> PhpPgAdmin). If this cannot be impl
> We are also waiting for a proper ALTER table DROP column but we are day
> dreamers...
This is a good example of bad management on our parts. We couldn't
decide between two possible DROP COLUMN implementations, so we now have
the worst result, which is no implementation at all.
--
Bruce Mo
"Jason Orendorff" <[EMAIL PROTECTED]> writes:
> Hi. I was surprised to discover today that postgres's
> character types don't support zero bytes. That is,
> Postgres isn't 8-bit clean. Why is that?
(a) because all our datatype I/O interfaces are based on C-style
(null terminated) strings
> "Ron" == Ron de Jong <[EMAIL PROTECTED]> writes:
Ron> Any idea to get a human readable list with column
Ron> descriptions like type,size,key,default,null.
Ron> It would be nice if it would look simular to the mysql
Ron> variant:
You'll need to write your own query to get i
Bruce Momjian writes:
> I recommend tips when they are one line in length, have a high
> probability of being accurate, and are common mistakes. Anything longer
> and we should point to a specific section in the docs.
I would put "when porting from MySQL" into that category.
--
Peter Eisentra
Use bytea. Search archives.
On Sun, 21 Oct 2001, Jason Orendorff wrote:
> Reply-To: sender
>
> Hi. I was surprised to discover today that postgres's
> character types don't support zero bytes. That is,
> Postgres isn't 8-bit clean. Why is that?
>
> More to the point, I need to store about 1
Bill Studenmund writes:
> Why? Operators are used differently than functions.
I don't think so. Operators are a syntacticaly convenience for functions.
That's what they always have been and that's what they should stay.
> Conceptually the main determiner of what function you want is the name,
Jean-Michel POURE <[EMAIL PROTECTED]> writes:
> Would it be possible to implement CREATE OR REPLACE VIEW / TRIGGER in
> PostgreSQL 7.2?
We're already vastly overdue for beta. The time for new feature
requests for 7.2 is past ... especially nontrivial requests.
regards,
Jason,
BLOBs as you have correctly inferred do not get automatically deleted.
You can add triggers to your tables to delete them automatically if you
so desire.
However 'bytea' is the datatype that is most appropriate for your needs.
It has been around for a long time, but not well document
On Sat, Oct 20, 2001 at 05:24:39PM +0200, Ron de Jong wrote:
> Not even close!
>
Oh? What's it missing? the \dt display in psql has all the information
in your mythical table versionbelow, just organized a little differently,
doesn't it?
Particularly on the hackers list, if there's a feature yo
Bruce Momjian writes:
> It was on the TODO list, and I did exactly what was listed there. What
> we have now is a discussion that the TODO item was wrong.
I don't consider the items on the TODO list to be past the "adequately
discussed" stage.
To the topic at hand: I find reversing the argume
Reiner Dassing <[EMAIL PROTECTED]> writes:
> explain select * from wetter order by epoche desc;
> NOTICE: QUERY PLAN:
> Index Scan Backward using wetter_epoche_idx on wetter
> (cost=0.00..3216018.59 rows=2034 width=16)
> explain select * from wetter where epoche between '1970-01-01' an
> Bruce Momjian writes:
>
> > It was on the TODO list, and I did exactly what was listed there. What
> > we have now is a discussion that the TODO item was wrong.
>
> I don't consider the items on the TODO list to be past the "adequately
> discussed" stage.
>
> To the topic at hand: I find re
(I've been following the thread, at least casually ;)
> Why? Operators are used differently than functions. That strikes me as a
> good reason to namespace them differently.
> Conceptually the main determiner of what function you want is the name, at
> least as far as from what I can tell from ta
"Command Prompt, Inc." <[EMAIL PROTECTED]> writes:
> Mainly, the existing documentation on the RENAME statement seems
> inaccurate; it states that you can re-name variables, records, or
> rowtypes. However, in practice, our tests show that attempting to RENAME
> valid variables with:
> RENAME va
On Tue, 23 Oct 2001, Peter Eisentraut wrote:
> Bill Studenmund writes:
>
> > Why? Operators are used differently than functions.
>
> I don't think so. Operators are a syntacticaly convenience for functions.
> That's what they always have been and that's what they should stay.
How does what you
Martin Weinberg <[EMAIL PROTECTED]> writes:
> Yes, I understand locking the table, but empirically, two index
> creations will not run simultaneously on the same table.
Hmm, on trying it you are right. The second index creation blocks here:
#6 0x1718e0 in XactLockTableWait (xid=17334) at lmgr.
"Jason Orendorff" <[EMAIL PROTECTED]> writes:
> Reply-To: sender
Just to be nice, I'll do this. ;)
> Hi. I was surprised to discover today that postgres's
> character types don't support zero bytes. That is,
> Postgres isn't 8-bit clean. Why is that?
As I understand it, the storage system i
> Not possible to accept both forms at present and issue a notice that
> LIMIT m,n is deprecated?
We accept both now and will for <=7.2. In 7.3, it will be only LIMIT #
OFFSET #.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 85
Dear all,
Would it be possible to implement CREATE OR REPLACE VIEW / TRIGGER in
PostgreSQL 7.2?
Alternatively, could someone implement CREATE OR DROP VIEW / TRIGGER? These
features are needed for pgAdmin II (we could also provide a patch for
PhpPgAdmin). If this cannot be implemented in Postg
Your <[EMAIL PROTECTED]> address bounced. Do you have another one?
Thanks,
Bill
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Reply-To: sender
Hi. I was surprised to discover today that postgres's
character types don't support zero bytes. That is,
Postgres isn't 8-bit clean. Why is that?
More to the point, I need to store about 1k bytes per row
of varying-length 8-bit binary data. I have a few options:
+ BLOBs.
Dear all, I am trying to install
PostgreSQL 7.1.3 on Win98 with APACHEand PHP (both installed and running),
andam getting errors with "make" and "make install" (see
below). What are the differences in installations for Win98, WinNT
and Win2000?There are so many procedures around and none is
Hello, I'm trying to set up a trigger on insert or update
but when using the predefined variable ``OLD'' I get a
NOTICE from the trigger function about OLD not being defined yet.
Of course OLD is not defined when the function is triggered on INSERT
event, and I did not mention it if not inside a
Yes, I agree perfectly... I never thought of that! I would really like it if some more
info was added to the docs regarding info on rules and triggers. The section on update
rules is quite good, but some more would never hurt. One point in the trigger vs rules
section which at least to me is ve
I have an idea for creating a Perl script, but I just wanted to make
sure that no one has already created something similar.
When doing a full row select, it's necessary to create all the bind
variables, and then do a column by column select statement. Ugly. I
want to automagically create an inc
Doug McNaught wrote:
> Reiner Dassing <[EMAIL PROTECTED]> writes:
>
> > Hello PostgreSQl Users!
> >
> > PostSQL V 7.1.1:
> >
> > I have defined a table and the necessary indices.
> > But the index is not used in every SELECT. (Therefore, the selects are
> > *very* slow, due to seq scan on
> > 20
Thanks, but latest Cygwin installation (using internet "setup.exe"),
although saying it includes PostgreSQL, does NOT.
There is a "nmake /f win32.mak" to be run under Visual C++ explained in
PostgreSQL Docs=Windows installation in order to build "libpq.dll" which
needs to be placed into "windows/
On Sat, 20 Oct 2001, Aasmund Midttun Godal wrote:
> Can a rule see the where statement in a query which it has been
> triggered by? or is it simply ignored?? what happens?
>
Looking over your question, I wanted to clarify the problem a bit, so:
(cleaned up example a bit from Aasmund)
-- set up
If you like the psql client then have a look at a graphical "psql" CGI
program!!!
It's just one file twdba.cgi to put in your cgi-bin directory and your
browser does the rest.
http://home.planet.nl/~radejong (TWDBA Download button)
You see the \? tricks only work with that particular psql client
Hello
psql
\dt employee
Should do the trick
"Ron de Jong" <[EMAIL PROTECTED]> wrote in
9qp2et$i7q$[EMAIL PROTECTED]:">news:9qp2et$i7q$[EMAIL PROTECTED]:
> Any idea to get a human readable list with column descriptions like
> type,size,key,default,null.
> It would be nice if it would lo
On Sat, 20 Oct 2001, Steve Howe wrote:
> Hello all!!
>
>
> I'm developer of a interface for PostgreSQL for the Borland Kylix
> and Delphi tools (http://www.vitavoom.com). I've run into the following
> problems with catalogs:
>
> - pg_group: the grolist field is an array. How can I
Not even close!
wrote in message 3bd02277$[EMAIL PROTECTED]">news:3bd02277$[EMAIL PROTECTED]...
> Hello
>
>
> psql
>
> \dt employee
>
> Should do the trick
>
>
>
>
>
> "Ron de Jong" <[EMAIL PROTECTED]> wrote in
> 9qp2et$i7q$[EMAIL PROTECTED]:">news:9qp2et$i7q$[EMAIL PROTECTED]:
>
> > Any idea t
I'm proud to announce you that the latest release of TWDBA now includes
PGSQL as well.
Download it from:
http://home.planet.nl/~radejong/
Further I would like to thank all those users for testing TWDBA and positive
feedback.
Listening to users is the only way to come to a good product...
Regar
> I agree completely with these points, which is why I'd rather have seen
> it dealt with (one way or t'other) in 7.2. But we appear to have a lot
> of people who don't think it's been discussed adequately in
> $PREFERRED_FORUM ... and the one thing I *really* don't want is to hold
> up 7.2 beta
Peter Eisentraut writes:
> Lee Kindness writes:
> > Touche, but the man page for the front-end (plain old cc) doesn't list
> > options and only refers to the acc man page ;)
> Well, I'm stumped. All the Solaris compilers I've ever seen did support
> and document the -Wl option.
Well I never
42 matches
Mail list logo
