> > > Andreas Pflug <[EMAIL PROTECTED]> writes:
> > > > - what about Oracle portability.
> > >
> > > > IMHO we should rethink if we could make those people happy. How about a
> > > > loadable personality (IIRC SAPDB has something like that), to exchange
> > > > the parser in use with a custom one (
Marc G. Fournier wrote:
On Tue, 6 Jul 2004, Andreas Pflug wrote:
An external tool helping translating sql is fine, but nothing to be
defined todo for core pgsql IMHO. I still believe some minor "oracle
helper" behaviour (not to call it oracle compatibility, to avoid
wrong expectations) should be
On Tue, 6 Jul 2004, Andreas Pflug wrote:
An external tool helping translating sql is fine, but nothing to be
defined todo for core pgsql IMHO. I still believe some minor "oracle
helper" behaviour (not to call it oracle compatibility, to avoid wrong
expectations) should be added. Currently, pgsql
Bruce Momjian wrote:
Gavin Sherry wrote:
On Sat, 3 Jul 2004, Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
- what about Oracle portability.
IMHO we should rethink if we could make those people happy. How about a
loadable personality (IIRC SAPDB has something like
Gavin Sherry wrote:
> On Sat, 3 Jul 2004, Tom Lane wrote:
>
> > Andreas Pflug <[EMAIL PROTECTED]> writes:
> > > - what about Oracle portability.
> >
> > > IMHO we should rethink if we could make those people happy. How about a
> > > loadable personality (IIRC SAPDB has something like that), to exc
On Sun, 2004-07-04 at 19:57, Tom Lane wrote:
> Anyone who needs this has always been able to make it trivially
> (though you once had to invent a random column name for the one
> required column).
In Oracle, DUAL is treated specially internally for performance reasons,
since it is so heavily used
Andrew McMillan wrote:
On Sun, 2004-07-04 at 13:11 +0200, Andreas Pflug wrote:
That's right, and initially they will only serve MySQL, but it will be
extendable to support any db system. It will be GPL (or licenseable, but
since it's a tool and not a platform IMHO GPL is ok).
If things work ou
On Sun, 2004-07-04 at 13:11 +0200, Andreas Pflug wrote:
>
> That's right, and initially they will only serve MySQL, but it will be
> extendable to support any db system. It will be GPL (or licenseable, but
> since it's a tool and not a platform IMHO GPL is ok).
> If things work out as they seem,
Kaare Rasmussen wrote:
That would be great news indeed. Currently there is a lack of an Open Source
heavy duty database design tool.
If it can be compared to Erwin, it will be a big win - if it can do both
reverse and forward engineering of databases.
It's is aimed to replace ErWIN or Ap
Mario Weilguni wrote:
Because their SQL queries always seem to need a target object to select
from. i.e. "SELECT NEXTVAL.foo" isn't valid for Oracle 8/9.
It has been a long time since I've used Oracle, but shouldn't it be "select foo.nextval from dual"?
Yep, that's sounds better. It's been a co
>
> Because their SQL queries always seem to need a target object to select
> from. i.e. "SELECT NEXTVAL.foo" isn't valid for Oracle 8/9.
>
It has been a long time since I've used Oracle, but shouldn't it be "select
foo.nextval from dual"?
Regards,
Mario Weilguni
---
Justin Clift <[EMAIL PROTECTED]> writes:
> There's also their "FROM DUAL" workaround (in common usage) as well.
[ yawn... ]
regression=# create table dual();
CREATE TABLE
regression=# insert into dual default values;
INSERT 292940 1
regression=# select 2+2 from dual;
?column?
--
Andreas Pflug wrote:
That's true, it's the question how much can be offered without too much
effort.
I'm not too deep in oracle stuff, what comes to my mind is
- outer join syntax (parser thing)
- sequences usage (parser too)
- maybe stored procedure call, with a wrapper to convert output
parame
> That's right, and initially they will only serve MySQL, but it will be
> extendable to support any db system. It will be GPL (or licenseable, but
> since it's a tool and not a platform IMHO GPL is ok).
> If things work out as they seem, I'd contribute the pgsql stuff.
That would be great news in
On Sun, Jul 04, 2004 at 12:10:52AM -0400, Alvaro Herrera wrote:
> You made me remember that some time ago a non-tech fellow presented me
> as giving a talk about "Postgresol" ... the audience had quite a laugh.
> It seems nobody thought about instructing him on how to pronounce the
> thing ... it
Bruce Momjian wrote:
Andreas Pflug wrote:
Jeroen T. Vermeulen wrote:
But like I said, that's just my personal conviction. I definitely think
people in our community ought to be willing to work together with the
MySQL people, the FireBird people and anybody else in the free world to
have wo
Andreas Pflug wrote:
> Jeroen T. Vermeulen wrote:
>
> >
> >But like I said, that's just my personal conviction. I definitely think
> >people in our community ought to be willing to work together with the
> >MySQL people, the FireBird people and anybody else in the free world to
> >have world-clas
Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
How about an external tool that helps in translating apps to
SQL-standard syntax? Oracle does accept the standard syntax after all.
Nice idea, but
- sources might not be accessible
- sources might not be easily readable (esp. i
Jeroen T. Vermeulen wrote:
But like I said, that's just my personal conviction. I definitely think
people in our community ought to be willing to work together with the
MySQL people, the FireBird people and anybody else in the free world to
have world-class GUI development tools;
Just a note:
I'
On Sat, Jul 03, 2004 at 11:33:35PM -0400, Mike Mascari wrote:
> The fact that novices can't pronounce the name correctly is a
> problem. People will be afraid to raise the possibility as a
> solution in the enterprise if they think they'll look like a fool
> pronouncing the name aloud. I rememb
Jeroen T. Vermeulen wrote:
That about covers the important stuff. Some more for the "other" bucket
(although they all came repeatedly):
- so how do I pronounce "Postgre"?
...
On the "Postgre" point, I remarked to some friendly people (who are
developing a content management system based on postgr
On Sat, 3 Jul 2004, Tom Lane wrote:
> Andreas Pflug <[EMAIL PROTECTED]> writes:
> > - what about Oracle portability.
>
> > IMHO we should rethink if we could make those people happy. How about a
> > loadable personality (IIRC SAPDB has something like that), to exchange
> > the parser in use with a
On Sat, Jul 03, 2004 at 05:59:17PM +0200, Andreas Pflug wrote:
> classifying the questions we got those three days in the PostgreSQL
> booth on LinuxTag, we had three ever repeating topics, two of them
> non-surprising:
> - what's the difference to MyS***
> - what about win32 native
> - what ab
Andreas Pflug <[EMAIL PROTECTED]> writes:
>> How about an external tool that helps in translating apps to
>> SQL-standard syntax? Oracle does accept the standard syntax after all.
> Nice idea, but
> - sources might not be accessible
> - sources might not be easily readable (esp. if not embedded s
Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> writes:
- what about Oracle portability.
IMHO we should rethink if we could make those people happy. How about a
loadable personality (IIRC SAPDB has something like that), to exchange
the parser in use with a custom one (by a SET comman
Dennis Bjorklund wrote:
Having two parsers would be a nightmare to maintain.
Probably. It just came to my mind because one visitor mentioned he would
look at the bison stuff to do it himself. I meant to enable him to do so
if he likes (and can) without hacking the core product.
If anything on
Andreas Pflug <[EMAIL PROTECTED]> writes:
> - what about Oracle portability.
> IMHO we should rethink if we could make those people happy. How about a
> loadable personality (IIRC SAPDB has something like that), to exchange
> the parser in use with a custom one (by a SET command)? This way we ha
On Sat, 3 Jul 2004, Andreas Pflug wrote:
> IMHO we should rethink if we could make those people happy. How about a
> loadable personality (IIRC SAPDB has something like that), to exchange
> the parser in use with a custom one (by a SET command)?
Having two parsers would be a nightmare to mainta
Dear developers,
classifying the questions we got those three days in the PostgreSQL
booth on LinuxTag, we had three ever repeating topics, two of them
non-surprising:
- what's the difference to MyS***
- what about win32 native
- what about Oracle portability.
The third question was asked from s
29 matches
Mail list logo
