.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 8: explain analyze
. Better to look over the code
again after a night of sleep.
Thanks a lot.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL
I have a problem with compile PostgreSQL from cvs with tag
REL7_4_STABLE
Error is 'ECPG_ARRAY_NONE is not declared' (in execute.c)
My fault. extern.h wasn't committed and I didn't notice. Sorry.
It should be fixed now.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ
it it will make it into 7.4.1
this way.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast
binaries? I think there are several
companies out there providing support for a given version of PostgreSQL
and doubt they all ask for their own binaries. At least we do not.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL
be included directly by some
apps.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast
one.
Does anyone know how Informix, where this file comes from, handles this?
Would it be a solution to just move the compat headers out of the main
include dir?
michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go
that you will alsways get our file and not the one in
/usr/include. That means you must not specify our -I option if you need
the file in /usr/include. Since this file may be needed together with
pgsql The best way seems to be moving just the compat headers IMO.
Michael
--
Michael Meskes
Email
. Peter is preparing
a patch that dave can test for us, so we hopefully get this into CVS
until Friday.
michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL
should either change the docs or start using override in
the Makefiles.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL
On Thu, Jan 01, 2004 at 01:59:45PM +0800, William ZHANG wrote:
in preproc.y:2021:
...
Thanks for the report. I just fixed it in HEAD and 7.4.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein
Just wanted to let you know that if we would be interested in adding
that patch to our main cvs the guy who wrote it would be more than
willing to change his license to BSD.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL
the
default rule again.
But then I wonder which inout flex thinks could trigger the default
rule. Any idea how to find out?
Bruce, Tom, or anyone else with flex 2.5.4, could you please run
/usr/bin/flex -s -o'pgc.c' pgc.l
and check if the same warning appears?
Michael
--
Michael Meskes
Email
, we have to maintain that list to make sure we get the right
connection.
Or what were you asking?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL
prefer to program my own default rule.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast
statement?
It would help me a lot if you'd be able to give some examples.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL
the AT statement does indeed allow a
variable as connection_target.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end
.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 8: explain analyze is your
On Fri, Apr 30, 2004 at 04:48:33PM -0400, Bruce Momjian wrote:
Does ecpg need to use the same timezone database as the backend?
I have to check what you changed. ecpg itself does not use the timezone
database, but some of that code is used in pgtypeslib.
Michael
--
Michael Meskes
Email
is released.
I will try to get some info from the bison people about the release
date.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1: subscribe
ecpg I would prefer to just remove
pretty obscure stuff and stuff introduced after 7.2 was released so we
won't break much. Does anyone have a list of newly added commands? Or do
I have to get the diff from CVS?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian
Just got this. :-)
Michael
- Forwarded message from Akim Demaille [EMAIL PROTECTED] -
To: Michael Meskes [EMAIL PROTECTED]
Subject: Re: bison 1.49 release
From: Akim Demaille [EMAIL PROTECTED]
Date: 25 Sep 2002 11:32:42 +0200
Michael == Michael Meskes [EMAIL PROTECTED] writes
* from sp_myproc() as table_alias([col definition list]);
Does this help any? Can he try the 7.3 beta?
Unfortunately no. They are not willing to use a beta so they are appearantly switching
to SAP DB. Sorry.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian
Hi,
I just learned that bison 1.50 was released on Oct. 5th and it indeed
compiles ecpg just nicely on my machine. Could we please install this on
our main machine and merge the ecpg.big branch back into main?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian
Could anyone please tell me if we found a solution? It seems I missed
any discussion or whatsoever. The only things I know is that
postgresql.org still has bison 1.35 installed and 7.3 release is
nearing.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU
a query that given the order in
the where clause either takes a few seconds or forever. Well, I killed
the query after quite some time.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast
Hi,
I just merged the big_bison branch back into HEAD. Hopefully I did this
in the correct way. Keep in mind that I'm not really fit in using cvs.
Please test it.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL
have bison 1.50 here too.
The changes are there already, I just have to fold the ecpg.big branch
into HEAD.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP
finding some docs about embedded SQL using
google or a similar search engine. As for PostgreSQL check the docs
about ecpg. There are also some examples in the source tree.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL
'
AND node_id != 0 AND NODE_NAME != :nodename; (line#493)
}
...
since its envelop'd in an if/else clause, shouldn't it work?
By definition no. You could compare it to C preprocessor commands like
#define.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire
slightly higher on their wish list.
This one surprised me too. Almost all companies I talked to abolut
PostgreSQL ask for PITR. Yes, many also ask for replication, but the
amount is much lower.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use
it would be very helpful to form a ecpg
connection on top a user supplied PGconn* object.
Why? It's possible, but you have to work with structures not meant to be
used outside the lib.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU
with the version numbering but I can fix that later.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
. The major number has to be inceased,
it's the minor numbers that need fixing. :-)
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1
On Mon, Jan 27, 2003 at 09:30:50AM -0500, Tom Lane wrote:
Michael Meskes [EMAIL PROTECTED] writes:
- Is it neccessary to patch c.h for ecpg?
If you commit that part, it will be reverted forthwith (especially the
hardwired #define HAVE_PTHREAD_H ;-)).
Keep the thread hacking on the client
On Mon, Jan 27, 2003 at 10:26:53AM -0500, Tom Lane wrote:
The preproc code doesn't need to be thread-safe does it?
You're right of cause.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL
. There shouldn't be much of a performance penalty.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 2: you can get off all lists at once
On Wed, Feb 19, 2003 at 12:29:12PM -0500, Tom Lane wrote:
SQL99. Looks like the parens got lost again by the time of the final
spec.
I don't think the parens really matter. It's just the different ordering
of columns and values.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ
On Wed, Feb 19, 2003 at 04:37:33PM +0100, Peter Eisentraut wrote:
That's not what my copy says.
Strange. I just looked at all the docs I have and all have it listed the
way Dave wrote. So I seem to have to update my docs. Peter, could you
send me a copy?
Michael
--
Michael Meskes
Email: [EMAIL
Informix actually implements.
Informix syntax is listed on
http://www-3.ibm.com/software/data/informix/pubs/library/visionary/infoshelf/sqls/01start.fm.html#156200
It's more than just parens IMO. :-)
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire
with it. That's why
they aren't committed yet.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 3: if posting/reading through Usenet
in this feature as you could always keep the numbers as
strings and let the database do all calculation stuff. But then you
cannot use the datatype in C.
And of course I don't like the idea of linking in the GPLed
GNU MP library on default as this would create licensing problems.
Michael
--
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
, feel free to use my [EMAIL PROTECTED]
address.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go
is '../lib' should become '../ecpglib'
in ecpg/preproc/Makefile, but am waiting on Michael to confirm.
You're right of course Tom. My first checkin was incomplete. I missed
some files when copying over to my cvs tree.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers
is required.
Of course the lib should then move out of interfaces, but ecpg could
still call it. Any comments?
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast
.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
:29. :-(
Maybe some of you have an idea.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
the new functions incorrectly. When calling them directly it seems
to work. Unfortunately I have no time to dig into it right now. But I
surely will soon.
Michael
--
Michael Meskes
Email: [EMAIL PROTECTED]
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL
I was just being asked if we are working on deletion of attributes in an
existing table. Something like ALTER TABLE foo DROP COLUMN bar. Is
anyone working on this, or are there design problems with it?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux
On Sun, Apr 14, 2002 at 10:15:50PM -0400, Tom Lane wrote:
Could this get cleaned up please?
Argh! Sorry, don't know how that typo made it in. I just fixed it.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL
Does anyone know if there is a way to extract the grammar and only the
grammar from a Bison file.?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 4
. Is there some kind
of roadmap available?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
statement by calling
ECPGfree_auto_mem(). But this is not documented and will never be.
The correct way is to free(array1) and free(array2) while libecpg will
free the internal structures when the next statement is executed.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use
for data.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister
.
Thanks in advance
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
. Maybe someone knows this. Else I will check in more detail.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
and couldn't even generate a decent bug report.
But at least you could send me a mail telling me something fails. :-)
I won't debug this if I don't know it fails.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end
[Moved to hackers}
On Sun, May 19, 2002 at 04:14:47PM -0400, Tom Lane wrote:
[EMAIL PROTECTED] (Michael Meskes) writes:
- Fixed reduce/reduce conflict in parser.
- Synced preproc.y with gram.y.
Good, but now I get:
$ make
bison -y -d preproc.y
preproc.y:5330: fatal error
a nonstandardly patched Bison would really suck :-(
I fully agree.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
attached gif I generated from grammar
extracted from the standard:
Well, the parser seems to be the easier part. :-)
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast
On Sun, May 19, 2002 at 04:19:58PM -0400, Tom Lane wrote:
Michael Meskes [EMAIL PROTECTED] writes:
Haven't found time to dig into this. So be careful, current CVS WILL NOT
COMPILE!
If you're not going to fix it right away, would you mind reverting the
commit?
Sorry, I just found
Hi,
I talked to one of the bison guys and he told me where to find a beta
version of bison 1.49. And this one translates the grammar without a
problem, no more table overflow. So once they will release the
new bison we should be able to expand our grammar.
Michael
--
Michael Meskes
[EMAIL
And this is with glibc 2.2.5. Of course this wouldn't be the first time
that RedHat uses the same version number for a different version.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast
to know what Debian should update.
Or do you mean that once Debian updates to glibc 2.3 (or whatever the
next release will be) it will show the same results? Does RedHat 7.3
already run on that new release? But then I would think they changed the
version number.
Michael
--
Michael Meskes
[EMAIL
On Thu, May 23, 2002 at 09:29:06AM -0700, Ulrich Drepper wrote:
On Thu, 2002-05-23 at 07:20, Michael Meskes wrote:
The glibc version in the soon to be released Woody
release is 2.2.5.
The version in RHL7.3 is 2.2.5-34. This is not what Debian uses. Maybe
you should read
I just looked at Bruce's talk about PostgreSQL history and saw the
flowchart slide. This would probably give a good poster too. Do we have
this flowchart available as eps, gif, whatever?
Or Bruce, do you have a version that you could send me?
Thanks a lot.
Michael
--
Michael Meskes
[EMAIL
it 2.2.6
or something if there has to be some changes that are not compatible?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
archive.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
one should I work on for solving
my problem.
Both will work and both will be efficient. ecpg internally uses libpq to
do the real work but gives you the standard SQL commands without having
to learn any new library API.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use
, create the table, and use the bulk copy interface.
Oh great! Talking about valuable comments. Ever bothered to even ask if
they are using triggers, constraints, etc. before coming with such a
proposal?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux
Hi,
there were several people at my talk asking if PostgreSQL is available
on Novell Netware. I know I read about someone working on this, but
didn't follow the thread at all since I do not have any Netware servers.
Does anyone out there know more?
Thanks in advance.
Michael
--
Michael
of
behaviour.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister
of the professional database systems.
The last time I used Oracle it used SQLCA in a very similar way as ECPG
does.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast
On Wed, Jun 12, 2002 at 05:42:24PM -0400, Bruce Momjian wrote:
You are actually the first person to complain about this, as far as I
can remember.
Yup. I cannot remember any other person either. And since nobody
complained, nobody worked on this. :-)
Michael
--
Michael Meskes
[EMAIL
will know the answer.
Actually I didn't know that test suite. But I will surely look at it.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 5: Have you checked our
solution. After all it hasn't
been released yet.
Since I suppose almost no one of you outthere uses a development version
of bison I cannot commit my changes, or else, you all cannot compile
ecpg anymore.
So what do we do?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire
, but I cannot get through
to you. Are you sure you use passive ftp for incoming connections?
Anyway, it seems you have to mail it. :-)
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast
How about we add the preproc.c file generated by bison 1.49 to cvs?
Could that create problems elsewhere?
The version that is part of the source tree now is generated on the
server, isn't it?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use
, but then it stopped and 1.49 is quite far from 1.35.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Tue, Jun 18, 2002 at 02:12:45PM -0400, Bruce Momjian wrote:
Are we the only ones up against this problem? Hard to imagine we are
No, there are more, that's why bison is worked on.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL
On Tue, Jun 18, 2002 at 04:41:57PM -0400, Tom Lane wrote:
Michael Meskes [EMAIL PROTECTED] writes:
How about we add the preproc.c file generated by bison 1.49 to cvs?
Could that create problems elsewhere?
Yes. It's a bad idea to put derived files in CVS. For one thing,
CVS
people at Red Hat? Maybe I could apply
a little internal pressure...
No idea, sorry.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1: subscribe
the
That would be nice. I do not really knwo cvs myself.
branch to be called.
No idea. new-bison maybe?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 5: Have
,
and JDBC
are trademarks or registered trademarks of Sun Microsystems, Inc. in the
U.S.
and other countries.
All SPARC trademarks are used under license and are
trademarks or registered trademarks of SPARC International, Inc. in the
U.S. and other countries.
Michael
--
Michael Meskes
[EMAIL
on mcvsup.postgresql.org. The file is owned by scrappy and has
no group write permissions.
It seems the file is still not writable. Or is there a mistake on my
side?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end
a version that
compiles ecpg grammar correctly.
No idea, if this will be fixed in the next month.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 5: Have you
difference seems to be the
name of the variable which in footest1 equals the attribute name.
Now I can guess what happens but I wonder if this is the desired
behaviour.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL
if there's a
way to make this kind of stuff more obvious for instance by using :login
for the variable as with embedded SQL. IMO the actual behaviour, while
of course correct, is a little bit confusing.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use
afraid.
Michael
P.S.: No repsonse by bison upstream yet, but I think he's on vacation
this week.
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1: subscribe
I just got the latest beta and it compiles ecpg grammar correctly! I had
to make one change to my source though as bison no longer accepts a comma inside the
token list.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL
if there
is a lot you can do about that, but it's a thought.
Will look at it.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands
how to fix this.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
variable?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
just not doing it before talking
to you guys.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http
. They just said as soon as possible. :-)
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
take the odbcplus code and put it into the odbc driver?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL
change
the backend compatible part of the grammar I either have to make the
same changes to the backends parser or ecpg will soon be unmaintainable.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
---(end
1 - 100 of 618 matches
Mail list logo
