> > This would help me, at least, write correct and portable SQL. :)
>
> Added to TODO:
>
> * Add a session mode to warn about non-standard SQL usage
So it seems that having C-like operators would hurt a lot;-)
So you want to generate warnings for SERIAL, TEXT and a bunch of other
types, W
On Thu, 8 Apr 2004, Tatsuo Ishii wrote:
> Are you talking about the sort order? Then there's no problem with
> encoding itself.
The tables in template1 in encoding E1 are compied into the new database
in encoding E2. Not all encodings are compatable, so you can't even
convert from E1 to E2.
--
Title: Message
Is there a log
reader for PostgreSQL that is documented?
This query
failed:
http://www.postgresql.org/search.cgi?ul=http%3A%2F%2Fwww.postgresql.org%2Fdocs%2F7.4%2Finteractive%2F%25&q=%22log+reader%22
Maybe another
terminology is used instead.
> On Wed, 7 Apr 2004, Tom Lane wrote:
>
> > If that were so, we'd not have a problem. The reason we have to tread
> > very carefully is that we do not know what tables/indexes users might
> > have added to template1.
>
> Aah, now I see the real problem!
>
> > If we copy a text index into a new
On Wed, 7 Apr 2004, Tom Lane wrote:
> >> solution, which is per-column locale settings within databases.
>
> > Of course, but that solution might be many years ahead.
>
> Peter E. seems to think that it's not an infeasible amount of work.
> (See previous discussion that he mentioned earlier in t
El Mié 07 Abr 2004 06:28, Fabien COELHO escribió:
> > > > =? as != is a synonum for <>, it would make sense.
> > >
> > > That was never such a terribly good idea, IMHO.
> >
> > Agreed. Compilers should give errors and not try to work around bad code.
>
> Is it bad code? Not for people who come from
Tom Lane wrote:
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
From what I can tell there is only 3 tables we talk about:
pg_database
pg_shadow
pg_group
If that were so, we'd not have a problem. The reason we have to tread
very carefully is that we do not know what tables/indexes users m
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> On Wed, 7 Apr 2004, Tom Lane wrote:
>> In any case, the whole idea is substantially inferior to the correct
>> solution, which is per-column locale settings within databases.
> Of course, but that solution might be many years ahead.
Peter E. seems to
On Wed, 7 Apr 2004, Dennis Bjorklund wrote:
> On Wed, 7 Apr 2004, Dennis Bjorklund wrote:
>
> Replying to myself here :-)
>
> > wants to import it into a 7.3 database. Use the 7.3 dump you might say,
> > but since BY does not do anything why not remove it from the dump output?
>
> I just reali
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> On Wed, 7 Apr 2004, Tom Lane wrote:
>> If we copy a text index into a new database and claim that it is sorted
>> by some new locale, we'd be breaking things.
> How is this handled for encodings? You can very well have something in
> template1 in an e
On Wed, 7 Apr 2004, Tom Lane wrote:
> If that were so, we'd not have a problem. The reason we have to tread
> very carefully is that we do not know what tables/indexes users might
> have added to template1.
Aah, now I see the real problem!
> If we copy a text index into a new database and claim
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Added to TODO:
> > * Allow locale to be set at database creation
>
> BTW, that is redundant with the locale todo items already present.
I see:
* Allow locale to be set at database creation
* Allow locale
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> From what I can tell there is only 3 tables we talk about:
> pg_database
> pg_shadow
> pg_group
If that were so, we'd not have a problem. The reason we have to tread
very carefully is that we do not know what tables/indexes users might
have add
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Added to TODO:
> * Allow locale to be set at database creation
BTW, that is redundant with the locale todo items already present.
regards, tom lane
---(end of broadcast)---
T
On Wed, 7 Apr 2004, Tom Lane wrote:
> And even more to the point, it would corrupt non-shared indexes
> inherited from template1. This could not be finessed --- AFAICS you'd
> need to do the equivalent of a REINDEX in the new database to make it
> work.
>From what I can tell there is only 3 tabl
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Because that would corrupt indexes on shared tables. (It might be
>> possible to finesse that, but it's not a no-brainer.)
> Oh, I hadn't thought of that. The problem isn't encoding, because we
> handle that already, but differen rep
Tom Lane wrote:
> Grant Finnemore <[EMAIL PROTECTED]> writes:
> > After an installation from CVS tip, I start the postmaster with the
> > -d(anything) flag. The postmaster starts up normally. I then try to
> > connect using psql, and either a TRAP is triggered (not using -A 0)
> > or an invalid cac
I said:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
>> I was asking why we can't set it to a new static value when we create
>> the database.
> Because that would corrupt indexes on shared tables. (It might be
> possible to finesse that, but it's not a no-brainer.)
And even more to the point, it
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I was asking why we can't set it to a new static value when we create
> > the database.
>
> Because that would corrupt indexes on shared tables. (It might be
> possible to finesse that, but it's not a no-brainer.)
Oh, I hadn't thoug
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I was asking why we can't set it to a new static value when we create
> the database.
Because that would corrupt indexes on shared tables. (It might be
possible to finesse that, but it's not a no-brainer.)
regards, tom lane
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Anyone know why we don't allow locale to be set per database?
>
> Changing it on the fly would corrupt index sort ordering. See also
> Peter's response nearby.
I was asking why we can't set it to a new static value when we create
th
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Anyone know why we don't allow locale to be set per database?
Changing it on the fly would corrupt index sort ordering. See also
Peter's response nearby.
regards, tom lane
---(end of broadcast)--
Karel Zak <[EMAIL PROTECTED]> writes:
> On Tue, Apr 06, 2004 at 10:33:25AM -0400, Tom Lane wrote:
>> This isn't simply a matter of "omitting the sort".
> I didn't talk about "Append" result, but about "Unique" result. The
> ORDER BY in UNION query works with final concanated data -- tha
Bruce Momjian wrote:
Dennis Bjorklund wrote:
Is anyone working to make the locale support in pg better? Running initdb
to set the locale is a bit heavy. It would be nice to at least be able to
set it per database.
Uh, createdb and CREATE DATABASE both have encoding options. initdb
only s
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 06, 2004 10:55 PM
> To: Dann Corbit
> Cc: [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Small suggestion on build script
>
>
> "Dann Corbit" <[EMAIL PROTECTED]> writes:
> > I would like to suggest changi
Dennis Bjorklund wrote:
> Is anyone working to make the locale support in pg better? Running
> initdb to set the locale is a bit heavy. It would be nice to at least
> be able to set it per database.
I was supposed to do that but I got distracted. I send out a longish
implementation and transitio
Dennis Bjorklund wrote:
> It would be useful with some flag/variable to set that makes pg
> generate varnings for non standard constructs. Unfortunatly there are
> so many things that are non standard, still using != instead of <>
> could be a usable warning.
This is a valid project; in fact it's
Dennis Bjorklund wrote:
> Is anyone working to make the locale support in pg better? Running initdb
> to set the locale is a bit heavy. It would be nice to at least be able to
> set it per database.
Oops, I confused locale and multibyte. Yes, I don't see a way to change
locale for new databases,
Bruce Momjian wrote:
SRA America is sponsoring an evening event with me in NYC. If folks
want to go, the details are on our web site under "Events".
I marked my calendar. If anyone wants to talk replication on the
sidelines, I'll be there.
Jan
--
#==
Dennis Bjorklund wrote:
> Is anyone working to make the locale support in pg better? Running initdb
> to set the locale is a bit heavy. It would be nice to at least be able to
> set it per database.
Uh, createdb and CREATE DATABASE both have encoding options. initdb
only sets the encoding for te
Grant Finnemore <[EMAIL PROTECTED]> writes:
> After an installation from CVS tip, I start the postmaster with the
> -d(anything) flag. The postmaster starts up normally. I then try to
> connect using psql, and either a TRAP is triggered (not using -A 0)
> or an invalid cache id is found (using -A 0
Stephen Frost wrote:
-- Start of PGP signed section.
> * Josh Berkus ([EMAIL PROTECTED]) wrote:
> > Were I teaching a class with a SQL component, using PostgreSQL as a tool, I
> > would be very careful to avoid letting my students use an extensions to SQL;
> > no "!=", no "SELECT DISTINCT ON" and
* Josh Berkus ([EMAIL PROTECTED]) wrote:
> Were I teaching a class with a SQL component, using PostgreSQL as a tool, I
> would be very careful to avoid letting my students use an extensions to SQL;
> no "!=", no "SELECT DISTINCT ON" and no alias references in the GROUP BY
> clause.
I'd really l
Fabien,
> Moreover, there are many SQL flavors around, so whatever the detailed
> syntax I learn them, it won't be the one they will have to face if the
> database they use is different. So why bother?
There are so many Java flavors around, why bother teaching the students syntax
at all? The fl
> There is a special display in my imaginary hall of fame of bad design
> decisions for the use of = and == in C and its blind adoption by C++,
> Java, Perl, etc, along with the associated use of "expr ;" as a statement.
>
> That's my view ;-)
Well, I agree with yout view about the C language des
On Wed, 7 Apr 2004, Fabien COELHO wrote:
>
> > > From my point of view, my students come from a java first course, so they
> > > have to learn again some new syntax and new operators. Small stuff, but
> > > it can help to say "same as java" and go on to new concepts.
> >
> > Don't you want them to
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> I just realized there is yet another new construct in 7.4. The sequences
> are created with NO MAXVALUE (and MINVALUE). Couldn't these just be
> removed in the pg_dump output in this case. It's the default anyway,
> right.
IIRC, these changes were to
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> On Mon, 5 Apr 2004, Tom Lane wrote:
>> However this could break existing queries that are relying on the
>> non-aliased behavior.
> This would be programs written for 7.4, In 7.3 and older the search order
> was (1), (2) and there was no (3) if I unde
Fabien COELHO wrote:
If you want to promote postgreSQL, then it should be good that anything
from outside (whether standard or not) can work with postgreSQL, but
anything that work in pg may not work outside;-)
I couldn't disagree more. What you are asking for is to do whatever (you
think) gets t
Fabien COELHO wrote:
From my point of view, my students come from a java first course, so they
have to learn again some new syntax and new operators. Small stuff, but
it can help to say "same as java" and go on to new concepts.
Don't you want them to learn SQL?
I want to teach them the
Fabien COELHO wrote:
> Is it better in /contrib or gborg?
Gborg imho. I thought we were trying to move all non-core code there
now. Isn't that why psqlodbc etc. were moved?
The argument was that it can be devopped and released independently?
Features in "contrib/" have a premium over external ad
> whilst I have, on rare occasions, observed the symlink
> failure under MingW, I've never come across the other issues
> you've mentioned (I build from cvs, instead of snapshots, but
> I can't imagine that causes these problems).
I'm running off snapshots (my bison install is badly broken),
Is anyone working to make the locale support in pg better? Running initdb
to set the locale is a bit heavy. It would be nice to at least be able to
set it per database.
--
/Dennis Björklund
---(end of broadcast)---
TIP 6: Have you searched our li
Hi all,
After an installation from CVS tip, I start the postmaster with the
-d(anything) flag. The postmaster starts up normally. I then try to
connect using psql, and either a TRAP is triggered (not using -A 0)
or an invalid cache id is found (using -A 0)
When I start the postmaster without the -
On Wed, 7 Apr 2004, Fabien COELHO wrote:
> From my point of view, my students come from a java first course, so they
> have to learn again some new syntax and new operators. Small stuff, but
> it can help to say "same as java" and go on to new concepts.
Don't you want them to learn SQL?
--
/Den
> > From my point of view, my students come from a java first course, so they
> > have to learn again some new syntax and new operators. Small stuff, but
> > it can help to say "same as java" and go on to new concepts.
>
> Don't you want them to learn SQL?
I want to teach them the concepts: relat
> > Is it bad code? Not for people who come from a C/C++/Java background.
>
> It's not the sql operator.
Yes.
> Every week I meet MySql people that want to port their application to
> another database and run into problems because they use some mysql
> construct instead of the standard sql cons
On Wed, 7 Apr 2004, Fabien COELHO wrote:
> Is it bad code? Not for people who come from a C/C++/Java background.
It's not the sql operator.
Every week I meet MySql people that want to port their application to
another database and run into problems because they use some mysql
construct instead o
> > > =? as != is a synonum for <>, it would make sense.
> >
> > That was never such a terribly good idea, IMHO.
>
> Agreed. Compilers should give errors and not try to work around bad code.
Is it bad code? Not for people who come from a C/C++/Java background.
They are used to operators such as =
On Wed, 7 Apr 2004, Peter Eisentraut wrote:
> > =? as != is a synonum for <>, it would make sense.
>
> That was never such a terribly good idea, IMHO.
Agreed. Compilers should give errors and not try to work around bad code.
Had the first generation of browsers done that we would have had a much
Dann Corbit wrote:
> I would like to suggest changing the symlinks to copy commands:
> The reason is that under Mingw, I get random failures with the
> symlinks (typically all will work but one or two, but there is no
> telling which will succeed and which will fail).
configure will automatically
Fabien COELHO wrote:
> Would it hurt anybody if operator == is made a synonym for operator
Yes, people would be induced to write incorrect code.
> =? as != is a synonum for <>, it would make sense.
That was never such a terribly good idea, IMHO. It might have gotten
carried over from PostQUEL.
On Wed, 7 Apr 2004, Dennis Bjorklund wrote:
Replying to myself here :-)
> wants to import it into a 7.3 database. Use the 7.3 dump you might say,
> but since BY does not do anything why not remove it from the dump output?
I just realized there is yet another new construct in 7.4. The sequences
In 7.4 there is an optional BY that are allowed in the definiton of
sequences:
CREATE [ TEMPORARY | TEMP ] SEQUENCE namn [ INCREMENT [ BY ] ökning ]
[ MINVALUE minvärde | NO MINVALUE ] [ MAXVALUE maxvärde | NO MAXVALUE ]
[ START [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE ]
(some swe
On Mon, 5 Apr 2004, Tom Lane wrote:
> This example strikes me as a good reason why we ought to deprecate and
> eventually remove the capability for GROUP BY to reference output-list
> aliases. This is not legal per SQL spec,
Sticking to the SQL spec is (almost) always good.
> matches. This wou
On Tue, Apr 06, 2004 at 10:33:25AM -0400, Tom Lane wrote:
> Karel Zak <[EMAIL PROTECTED]> writes:
> > I'm surprise with query plan that PostgreSQL planner prepare for
> > selects with ORDER BY if all data are from sub-select that is already
> > sorted.
>
> This isn't simply a matter of
Dear hackers,
Would it hurt anybody if operator == is made a synonym for operator =?
as != is a synonum for <>, it would make sense.
If it does not hurt, should it be implemented by replicating pg_operator
entries, or would a backend modification be ok? Operator != is NOT in
pg_operator, so it m
> I have a database with about 250,000 entries in a table, PG 7.5, One
> of the fields is text. LIKE queries on this field execute much faster
> than the equivalent regex queries.
>
> Is this what you would expect? Should I prefer LIKE to regex?
> (I'm a regex fan, but the performance hit seem
58 matches
Mail list logo
