m didn't even start. Honestly I fail to see how
this could be a bug in PostgreSQL. Are the libraries and the program compiled
with threading enabled? What happens if you use a very small test case instead
of your program?
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael
s to a valid numeric datatype. Suggestions?
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at googlemail dot com
VfL Borussia! Força Barça! Go SF 49ers!
The actual number is quite a bit lower because only variables used in DECLARE
statements directly get stored in that list.
> ** Bug Fixing:
> ** A new function should be added, details as folloging
I integrated this into the connection closing code.
Michael
--
Michael Meskes
Michael at
#x27;s a simple fix, although I
> ...
Changed in our master branch. Thanks for bringing this up.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at googlemai
at only emulated prepare statments. I've removed the checks for all
versions starting at 8.4. The next release should be fine for you.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postg
.
We added that to make sure we support the same embedded sql sourcecode on all
systems no matter if they have long long or not.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jab
ed to BUG #5464: ecpg on 64bit system converts "long long" to
> "long"
Well, this bug is (at least I don't know otherwise) fixed for more than a year.
Maybe the configure test doesn't work on Windows? I don't know.
Michael
--
Michael Meskes
Michael at Fam-Me
; back to the original locale in some error cases. I can see two
> returns from the function that neglect that, on lines 1776 and 1803
> in execute.c.
Fixed.
Thanks for spotting this.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at B
On Sat, Jul 16, 2011 at 09:21:04PM +0900, Akira Kurosawa wrote:
> I built PostgreSQL 8.4.8 with the following patch,
> then executed same program.
Thanks for the patch, applied.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at Borus
te Breite hat, versuchen Sie den "
> ! "Modifikator »FM«."
>
> #: utils/adt/formatting.c:1886 utils/adt/formatting.c:1899
> #: utils/adt/formatting.c:2029
Applied, thanks for the patch.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes d
ersion of your test case? Do you have
THREAD_SAFETY compiled into PostgreSQL?
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at googlemail dot com
VfL Borussi
ler
>
> I think it wouldn't be very difficult to calculate the dimension of "dim"
> dynamically (strlen(dimension) + 2)
Thanks for spotting this, I have no idea why this fixed size limit is in there
anyway. I will remove it.
Michael
--
Michael Meskes
Michael at Fam-
be
} SItemInfo; ?
> EXEC SQL SELECT name INTO: FROM sitem delivery;
Dito here..
> At C code does not exist in the structure sizeof (struct
> varchar_strNome_509) because
> she 'and a member of struct SItemInfo in the above case.
Sorry but I do not understand what you're sa
agile anyway.
I agree. How about adding a macro definition explicitely checking for the real
variable types?
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes
I'd apply full for HEAD and quick for 9.0 and 8.4. Will
you commit this? Or shall I?
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at googlemail dot
reported, it worked for ecpg (PostgreSQL 8.3.8)
4.4.1.
You seem to be answering to an email that I didn't see and couldn't find
in the archive either. Was it send in private or to the list? If it went
to the list I might be lagging behind.
Michael
--
Michael Meskes
Michael at Fam-
On Sun, Sep 05, 2010 at 08:21:48AM +, Alexander Pyhalov wrote:
> The following bug has been logged online:
>
> Bug reference: 5643
> ...
Just for the record, this bug has been identified to show a local maybe FreeBSD
related problem and not a PostgreSQL problem.
Michael
ocess WHENEVER NOT DATA FOUND
> Details:
>
> I have test program in embedded SQL, which works perfectly on 8.4.3 server
> and 8.4.0 client, but refuses to work on 8.4.4.
> ...
Could you please send me a test case so I can reproduce the problem here?
Michael
--
Michael Meskes
I guess the described problems are identical. Feel free to apply the memleal
patch.
Michael
"Kevin Grittner" schrieb:
>"Marcelo Mas" wrote:
>
>> Valgrind reports memmory leak when getting decimal data.
>
>I wonder how much overlap there is between this and the patch for
>fixing ECPG memor
,
8.4 and 9.0, so the next release will work as expected.
Thanks for spotting this.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jab
> > I'm currently without real access to a 64bit system until I come back home.
> > If
> > it is 64bit on *all* 64bit systems the problem is slightly different.
Just committed a patch to HEAD that hopefully fixes the problem.
Michael
--
Michael Meskes
Michael at Fam-Me
s the problem is slightly different.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org
VfL Borussia! Força Barça!
n't
seem to be that way on 64bit systems nowadays. I will check to see if there is
an easy fix. If it is fairly interruptive the fix won't make it into 9.0
though.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De,
e_from_asc in src/interface/ecpg/pgtypeslib/timestamp.c
>
> why isn't this picked up although I add it to source file list.
You need to link against libpgtypes. src/interface/ecpg/pgtypeslib/timestamp.c
does not belong into libecpg.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De,
the patch is attached.
Thanks for reporting.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: mes...@jabber.org
VfL Borus
On Sat, Nov 07, 2009 at 06:56:36PM +, Viisard wrote:
> Description:ecpg - cursor with regexp containing '.*/' fails to
Fixed in HEAD and 8.4.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot
open command in PostgreSQL. Instead the
declare command opens the cursor which is why the declare is called in the
position open was listed.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql)
hank you for reporting.
Fixed in CVS HEAD.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: mes...@jabber.org
Go VfL Borussia! Go S
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: mes...@jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
--
ve more than
one to test)? Do you recompile on amd or use the same binary? This might be a
compiler optimization problem as well, could you try using different -O values
for gcc?
I can do some debugging as well, but have to either reproduce this on my system
or getting onto yours. :-)
Michael
or CURSOR FOR SELECT name,id FROM m_table4;
I might be missing something here, but where do you see the bug? The cursor is
indeed already defined.
> 2- Preprocessor throws this error;
>
> *ERROR: syntax error at or near "-"*
> ...
Fixed in CVS. Thanks for the report.
Micha
it still is a GNU extension as GNU has for
quite a long time.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go
the old versions had a bug in that they accepted a variable there.
Can you use EXECUTE and put the whole statement into a variable instead?
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot
when the new
varchar naming was introduced.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go VfL Borussia! Go SF 4
t all because there is only one failure possible in initValue
and that's ENOMEM. So an application might not free all its memory if it ever
runs out of memory. But given that the latter case will probably result in the
application being terminated the effect is nil for almost all use cases.
Michael
ixed it in CVS for 8.2, 8.3 and HEAD.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
--
Sent via pgsq
E Linux 10
> Description:ECPG Selecting table with NULL values
> ...
This proofed to be a typo in the test case. Bug solved.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PRO
ns in the select query does not have to match the real order in the
> table of the database. Workaround is to reorder all columns in the ported
> code.
I just created my own test case from this small bit of information and
it works flawlessly. Would you please care to elaborate?
Mich
hen not using INFORMIX
mode? Do you use the "-r no_indicator" option?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go VfL Borussia! Go SF 49ers! Use Debian GN
I just committed the attached small fix to CVS HEAD and the 8.3 branch.
This should fix your problem.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go VfL Borussia! Go SF
7;t work in 8.3 anymore. You need to cast before calling the
> function, ie, func(col::inet).
> ...
However, this doesn't explain why ecpg fails to generate valid C code.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 1791
On Thu, Feb 14, 2008 at 11:13:53AM -0500, Tom Lane wrote:
> Michael, we branched 8.3 yesterday, so you need a third commit if you
> don't want people to see a regression from 8.2.7 to 8.3.x.
Thanks for the note, just committed to 8.3 branch as well.
Michael
--
Michael Meskes
Email:
Hallo Christoph,
On Thu, Feb 14, 2008 at 11:09:11AM +, Christoph Dalitz wrote:
> Description:ecpg lacks SQLSTATE macro definition
Thanks for reporting this oversight. I added the definition to CVS, also
for 8.2.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Mich
e isn't allowed on the backend side.
Older versions of ecpg created the statement by replacing the variables
on the client side, so this didn't matter at all.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo
g this a little bit?
The example works like a charm on my Linux system. It seems I should
setup an XP test bed too. :-)
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF
- At this point, the SQL statement has been prepare'd by PQlib,
> either when the statement was executed in the past, or in
> the previous step.
>
> - call "PQexecPrepared", using the array of parameters built
> in the first step above.
Do
see "CDECIMALTYPE" defined in sqltypes.h.
Could it be that there is a sqltypes.h file somewhere else on your
system?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go S
which version
you are using.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
--
ince it's such a small patch I also
committed it to 7.4, 8.0 and 8.1.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use Postgre
Am Freitag, 17. März 2006 09:36 schrieb Michael Wolff:
> The following bug has been logged online:
> ...
> Description:ECPGlib: Wrong error code in case of a duplicate key
Just fixed in CVS HEAD. Thanks for your report.
Michael
--
Michael Meskes
Email: Michael at Fam-Mesk
32/pei AS myconn USER
> pei IDENTIFIED BY 'geheim';
>
> (Or perhaps with single quotes, but that doesn't make a difference.)
The example with the single quote is incorrect. I just changed the docs
accordingly.
Without the single quotes though, the statement should work.
has been declared but ot opened
>
> The warning message looks like garbage insterted after the StoreCur name.
This of course is true and need to be fixed. However, on my system it
does not happen:
a.pgc:27: WARNING: cursor "StoreCur" has been declared but not opened
Could you p
elease?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of bro
; doesn't get fixed it means that I will need to run CPP over the code
> before I run ecpg, which is just ugly.
Can't you just compile a new version of ecpg with the patch Bruce
committed? Depending on the system you're using I could even send you a
binary.
Michael
--
Michael Me
sorry about that.
On the other hand I agree with Tom. Fortunately it's not a data corruption
problem.
:-)
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go
reprocessor are you using? I wonder if such a logic should better
be implemented in the Cobol-C transition instead.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers
use a file handle
> > obtained by using fopen
Could someone with access to a Windows system have a look at this? I do
not have one atm. In particular I'd like to know whether it makes a
difference if your compiled ecpg with threading enabled or not. After
all without threading the fun
On Sat, May 07, 2005 at 12:37:24PM -0400, Bruce Momjian wrote:
> Are you still seeing a failure in ecpg? I ran your test here and got:
> ...
Bruce,
this is fixed AFAIK. I just never saw the original post on -bugs and
thus did not answer there either.
Michael
--
Michael Meskes
Email: M
Patch committed. Thanks.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end
On Thu, Feb 10, 2005 at 01:05:18PM +0900, TANIDA Yutaka wrote:
> Probably, "create sequence" and "create domain" have same problems. Here's
> a patch for preproc.y .
Or at least very similar ones. :-)
Thanks a lot for the report. Patch committed to CVS HEAD and 8
h. 7.4 does not suffer from this bug.
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)
e to allow it in
ecpg. But there are some patches that implement
the feature on gborg afaik.
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
. But I'd prefer to keep it that way and not risk a bigger
problem.
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!
---
om. 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!
---(end of broadcast)---
TIP 2: yo
On Mon, Jan 24, 2005 at 03:24:13PM -0500, Tom Lane wrote:
> Edmund Bacon <[EMAIL PROTECTED]> writes:
> > njamd says:
> > NJAMD/free: Double free of address 0x41454ff4
>
> > #4 0x40021e87 in free () from /usr/lib/libnjamd.so
>
> OK, here's where I d
n
or the next release candidate should fix the problem. I'm sorry, but I do not
have a patch against 7.4 at the moment.
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/Linu
ain. That is you can also
write EXEC SQL CONNECT to connect to the default database using the
given username.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Thanks for the report.
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: e
On Tue, Sep 14, 2004 at 08:35:52AM +, Valerie Schneider DSI/DEV wrote:
> But why ecpg found it in the 7.4 version ?
I'm not even sure this is the reason. Could you please try moving the
file to "." to see if it works?
Michael
--
Michael Meskes
Email: Michael at Fam
t then it should also print that.
I had the file in "." where ecpg found it and the constant was correctly
translated.
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 De
I received this bug report and will take care of it as soon as I find
time. Since I am travelling next week to give PostgreSQL training, this
will take at least a week or so.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL
On Wed, Aug 11, 2004 at 06:51:59PM -0400, Tom Lane wrote:
> Looks like a slip-up in copying a change from the main grammar. I've
> applied the attached patch to fix it. Thanks for the report!
Thanks Tom.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304
On Fri, Jul 23, 2004 at 03:49:30PM +1000, Luke McFarlane wrote:
> Although if you are to support INFORMIX or INFORMIX_SE mode in ecpg you
> will need limit it to 'SQL' space (for these modes anyway).
Didn't know that. Thanks for the info. Patch committed to CVS.
Michael
--
to define most things twice.
> Also, if you try to fool ecpg by compiling with ecpg -D SYMBOL=SYMBOL it
> will sit in an infinite loop gobbling as much virtual memory as it sees fit.
Ah yes, another bug.
I just committed a fix for this as well.
All fixes went into HEAD and 7.4.
Michael
On Sun, May 02, 2004 at 07:50:46PM -0400, Tom Lane wrote:
> >> [BUG] memory leak on error path (dtype != DTK_DELTA)
> >> File where bug occurred:
> >> postgresql-7.4.2/src/interfaces/ecpg/pgtypeslib/interval.c
>
> > Looks suspicious to me, but ECPG is Michael
rectly.
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 4: Don't
ng this feature. On
the other hand I see no reason why setting the len to 0 in case of a
NULL could be a problem for ecpg. But please keep in mind that you are
getting NULLs from the DB, not empty varchars, even if they look that
way in C.
I will commit the patch in a few minutes.
Michael
--
M
I have no
Informix myself so I need to know how Informix reacts to this test case.
Also, you know that you hve to specify "-r no_indicator" for this to
work I assume.
> Generally though, I've been unable to find any documentation on the
> Informix-compatibility mode.
Unfo
nation, this option came in as a compatibility option to
Informix. But it can also be used without Informix as you see. I wonder
if I should make this option only callable in compatibility mode.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes,
his is my fault as I was
too busy to seriously review the patch.
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
ting?
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 3: if posting/
d a fix to HEAD and
REL7_4_STABLE so it should be in 7.4.2.
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!
-
ects a character string since the
variable is char[]. Seeing that it gets more than one value it tries to
bulk load the data into an array of strings which obviously doesn't
exist.
I will have to see what solution is best for this.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ
On Sun, Feb 29, 2004 at 09:22:45PM +0100, Margit Schubert-While wrote:
> Actually caused by undefined variable later in the code.
> Sample prog sent to Michael.
Sorry, forgot to tell you that I fixed this. Should be in latest CVS,
HEAD and 7.4.
Michael
--
Michael Meskes
Email: Michael
y other RDB preprocessor that I have
> tried doesn't have this problem.
And that makes it a bug? I would accept this as a missing feature. But
even then seeing how the variable is used would help seeing if we can
implement this.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot
h code to run a simple test. It shouldn't be
too difficult to include the variable declarations so it's at least
compilable code.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! U
at were missing. So if you find another one please
tell me.
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!
-
bug and committed the fix to CVS, but I cannot tell now
if it also fixes your problem.
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!
--
n both dyntest and dyntest2.
> Both ran without problem.
Glad to hear that.
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!
---
at won't be enough, as I can send you all things
to test via email as well. The problem is that this has such a long
turnaround. If I could access the machine, or another one with this bug,
myself, I could test debug the whole stuff.
Michael
--
Michael Meskes
Email: Michael at Fam-M
ne? The code looks
okay to me. At the moment I have no idea what's going on.
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 Mon, Dec 22, 2003 at 09:33:00AM -0500, Mark Pether wrote:
> If that's the case then you'd better change your documentation...
Fixed. Thanks for pointing me to this.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, J
doesn't work I will add this
to the ecpg todo list, but I wouldn't say we guarantee that all C++
constructs work with ecpg.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go
e "log"
dyntext produces?
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)-
On Wed, Dec 17, 2003 at 03:14:31PM -0500, Mark Pether wrote:
> Ecpg pretty prints my code causing compile errors.
Please note that ecpg is a precompiler for embedded SQL in C not C++.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jab
="-D_GNU_SOURCE -DALLOW_ABSOLUTE_DBPATHS" allo
or some other way that ensures the entry in Makefile.global is not
discarded.
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
he standard
clearly says that a cursor is created with an open call, so you surely
have to use open somewhere to use your cursor.
However, it certainly is no bug if you declare a cursor that is not
used.
Interestingly though, yours is the first complaint about this unless I
forgot all the others.
Mi
understood me. I wasn't talking about libpq but about libpgtypes.
The latest libecpg should depend on libpgtypes. Since yours doesn't I
wonder which on you link to your program.
Could you please tell me which version of libecpg you are using?
Michael
--
Michael Meskes
Email: Michael at
becpg. It also needs libpgtypes. Since you don't include this i wonder
if you link against an older libecpg.
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!
problems with this test case?
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)
1 - 100 of 103 matches
Mail list logo