from 2013?
Sorry, it seems I missed this email. Yes, the code should be
thread-aware, at least I don't know of any problems with it. It appears
to me that the docs haven't been updated by the patch that made ecpg
work with threads back in the day.
Michael
--
Michael Meskes
Michael at Fam-Me
s going on. We are more than willing to dig
into it, but we need more to be able to.
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/Li
some more info about your source code? Do
you use descriptors? Auto allocating?
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/
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
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!
---(end of broadcast)-
lect i from test where j = ( select j
> from test)
> LOG: unexpected EOF on client connection
> ERROR: relation "nonexistant" does not exist
> STATEMENT: select * from nonexistant
These errors are supposed to be there. Comments in the code even tell
you why.
Michael
-
n live with the slightly inconsistent
variable handling I think.
Expect a patch soon.
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 G
the
statement to a string and thereby replace the count variable with its
content and then EXEC SQL EXECUTE the string variable should do the job.
Hope this helps.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo:
ment_type'
> crbembsql.pgC:254: error: initializing argument 6 of `bool ECPGdo(int,
> int, int, const char*, char, ECPG_statement_type, const char*, ...)'
It seems that some compilers don't like int/enum aliasing here. I
changed this in CVS could you please re-try?
Michael
On Thu, Oct 18, 2007 at 04:46:00PM -0700, Steve Crawford wrote:
> ECPG - Embedded SQL in C ??
Correct. And the PG part should be obvious. :-)
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rh
essantially only call
the above mentioned functions:
int
rsetnull(int t, char *ptr)
{
ECPGset_noind_null(t, ptr);
return 0;
}
int
risnull(int t, char *ptr)
{
return (ECPGis_noind_null(t, ptr));
}
Hope this helps.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot
rting it.
What happens is that ecpg defines the data types, but does not use that
define while in C code. I just committed patches to CVS. I also attach
it here. Could you please try if this fixes your problem?
Thanks.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Mes
ite:
/* use indicator in insert */
exec sql insert into test (id, str, val) values ( 2, 'Hi there', :intvar
:nullind);
So this is essantially the same as with fetch.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM
d the tests. That's why I prefer to have no platform
specific expected files.
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
On Wed, Aug 23, 2006 at 11:41:50PM -0600, Michael Fuhr wrote:
> Is there a reason this server-side code is using ECPG instead of SPI?
To make sure it doesn't work? There is NO guarantee that ECPG will work
in this scenario.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De,
uld support single quotes
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 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end o
is way more different so I'd prefer to not touch it anymore.
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
On Wed, Aug 16, 2006 at 11:40:40AM -0400, Jasbinder Bali wrote:
> [2998]: ECPGexecute line 97 Ok: INSERT 0 1
This is a backend message saying that the insert command was executed error
free and inserted one record.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael
quot; documentation:
Ah, I see. It lacks the size information. Yes, this is a documentation
bug. varchar is translated to a struct with an char array whose size
needs to be given. I think it never worked without it.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes do
" that the preprocessor
> rejects with "ERROR: pointer to varchar are not implemented."
Do you have an example? This surely looks like a bug.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: mi
achine with the same connection setting.
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!
ror-prone to use a (single-quoted)
> string literal or a variable reference.
>
> which might be the source of confusion here.
This should be fixed. You're absolutely right.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ
The correct syntax would be:
EXEC SQL CONNECT TO tcp:postgresql://192.168.0.123/xyz USER jsb;
This should work at least it does for me. :-)
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
led with
ecpg also do not need a server on the same machine, why should they?
This is why Debian for instance has a seperate ecpg package.
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
am confused. STDOUT is already implemented. It was STDIN that we
> were asking if it was valuable.
Yes, I was asking about FROM STDIN. TO STDOUT has been added lately.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Y
On Wed, Aug 02, 2006 at 12:03:45PM +0200, Florian Weimer wrote:
> * Michael Meskes:
>
> > COPY TO STDOUT has been implemented, but I'm unsure whether COPY FROM
> > STDIN really makes sense. Does anyone know a real life example where
> > this would be needed and the
ould be needed and the work couldn't be done easier using psql?
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/Li
27;ve already done.
How about giving us at least the table definition and the system
information? Yes, I know I asked for those in my last email too. And
please tell us what makes you sure it doesn't work? Just no output?
Or empty output?
Michael
--
Michael Meskes
Email: Michael at Fam-Mes
I hear about this. You could run your
program with debugging enabled (see test/*.pgc for example). Also I'd
like to know which version of ecpg you're using.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo:
On Mon, Jun 12, 2006 at 11:14:24PM -0400, Peter L. Berghold wrote:
> what I don't see is how to detect that I've fetched the last row from a
> query. Is there more complete doco on this process somewhere?
Just look for "exec sql whenever not found ..."
Michael
n looking for support
would be http://www.postgresql.org/support/professional_support ? :-)
There are support companies in France and other parts of Europe which
might be a better idea for a company in France. After all I think a
situation like this might need some on-site availability.
Michael
--
M
ould be the
case. :-)
So to see if ROLLBACK has the behaviour you need you have to check the
backend documentation.
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
O? Anything else?
Yes, please add it. I do have some more open bug reports/feature requests, but
I'd like to reproduce things first before we add to the docs. Sometimes it's
easier to fix it than to add it. :-)
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael
will become better in the near future.
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!
---(e
Am Mittwoch, 1. Februar 2006 15:46 schrieb Noble, Robert:
> I get the following error from ecpg when it encounters a structure
> containing a bit field:
> ...
A quick guess would be that the parser simply doesn't know this syntax. I'll
have a look at it.
Michael
--
M
rce code?
Yes, there us an example directory in the source code:
.../src/interfaces/ecpg/test
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
u could sync the slave
back to the master it would be a master itself.
> I think I´m looking for a master-slave assynchronous solution. I know
> pgReplicator can do it, but I think the project is not active any more.
But Slony does master/slave replication.
Michael
--
Michael Meskes
Emai
rent output engine.
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 o
r not to use the -C compatibility option. I rather have a complete
> port and get away from INFORMIX.
There is. You can use PGTYPEStimestamp_from_asc instead. You just have
to link against pgtypeslib.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|C
all in the US.
> > Go Rhein Fire!
>
> And that?
My favourite and local NFLE team, that's professional (more or less)
american style football in Europe.
> > Use PostgreSQL!
>
> Yes, when Embedded SQL works again :-)
Okay, let's work on that one. :-)
Mich
to calls of malloc/free/realloc issued by libpq.
I would be happy to help debugging this. But up to now I didn't even
know about this problem. Could you please send me a test case so I can
reproduce this? Also did you try using 8.0?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot
on this?
I will try if you could send me an example to reproduce the problem. As
you said it does not happen on a small self written test case. Maybe you
can send me one of your source files stripped down to just connect.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 17914030
these constructs are used. If they are used inside an
SQL declare section it will probably cause trouble as ecpg does not know
them.
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 Debi
uld provide a snippet of the code or
even better a small 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
On Fri, Dec 26, 2003 at 02:04:09PM -0400, Marc G. Fournier wrote:
> One thought for future booths would be to have a "group photo" done that
> we can add to the web site ... ? :)
Yes, good idea. :-)
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 1791
On Thu, Dec 25, 2003 at 06:25:34PM -0400, Marc G. Fournier wrote:
> whose manning the booth?
The one one the photos is Noel Koethe. He manned the booth together with
Peter Eisentraut and me.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmes
gic to just lowercase
everything as this is not requiered IIRC.
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 broad
On Wed, Nov 19, 2003 at 11:16:18PM -0700, [EMAIL PROTECTED] wrote:
> Turning OFF AUTOCOMMIT as suggested didn't solve the problem.
Sure as it is OFF by default. You have to turn it ON.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: micha
rks fine. It is correct
Depends on what test.h contains. ecpg has to learn the definition of
your struct somewhere.
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 G
else should
it lear about your struct definition? You can of course use a EXEC SQL
TYPE command to define it for ECPG as well.
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
#x27;ecpg -t'.
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 9
ded stuff need to take a look at this!!
They just did. They even used their spare time to create a test case
themselves as you did only provide code snippets.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go
lls. In these calls just
replace the ET_ERROR with ET_FATAL. That's it.
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!
---
s the thread
Neither am I, so I have no idea where to look.
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
0.005.
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 9: the planner
xes.
As a matter of fact we use EXEC SQL IFDEF, ... and do not parse any
C/CPP code. running cpp before parsing leads to undesirable side
effects.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein
. What I meant to say with LGPL is that this license is for
such a usage, not that MySQl has LGPLed stuff.
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
7;s an
LGPL.
But since MySQL is double licensed and GPl is just one of the two it
gets even more complicated.
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 Deb
Please see the attached file for details.
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
he very same appearance?
> So the trial to move from Oracle8i to PostgreSQL 7.3.3 will be probably
> delayed until the possibility to do that (PL/PGSQL packages), he will
> try to ask the developpers to add ODBC in their apps.
How do they connect now? Native Oracle OCI?
Michael
--
ter seeing this stuff in another
project.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)-
how free software development works, jump into a project and
try to change it all, just to disappear after a few weeks.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fi
> - ECPGcommit(__LINE__);
But the translation is not correct anymore.
> - exec sql rollback;
> -
> - and is translated on the output to
> -
> - ECPGrollback(__LINE__);
Same here.
These functions have been combined to
ECPGtrans(int lineno, const char *connection_n
/bin/enable_lang plpgsql --all"
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://www.postgresql.org/search.mpl
uld work. But be sure to use the latest CVS version as there was a
> > small bug in this bug. I'm actually committing the fix right now.
Should read "bug in this part" of course. :-)
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhe
in declare section;
struct {
int id;
char value[40];
} *pmr;
exec sql end declare section;
This should work. But be sure to use the latest CVS version as there was a
small bug in this bug. I'm actually committing the fix right now.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
from libpq (it's still in there I think) and do the parsing
> before calling PQsetdbLogin().
This is a possibility of course. But why should this syntax be taken away
from other apps using libpq?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
"biblioteka" , NULL ,NULL, 0);}
So this of course brings me to wonder which version you are using.
> But that is wrong, it should look like this:
>
> --8<--
> { ECPGconnect(__LINE__, "biblioteka" , NULL , NULL ,NULL, 0);}
> --8<--
As it does.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
On Sat, Oct 07, 2000 at 12:51:54AM +1100, Danny wrote:
> 1)Does Postgresql with with UNIXODBC ?
Yes, it does without a problem.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
created autiomatically.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
sr/local/pgsql/include/sqlca.h
> )
>
> The error message turns up even when I use ecpg -I/usr/loca/pgsql/include
I'm at a loss here. I never expereienced something like this. What happens
if you install sqlca.h into '.'?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
ds an aggregate.
But the above query certainly does solve the ancestor problem.
Does anyone have an idea how DB2 executes such a statement?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
error Could not connect to database in line 25.
>
> What am I doing wrong? Yes, the database does exist as tootle.
Yup, that's one of those Oracle compatibility hacks. If you use connect
without 'to' ecpg expects the following term to a oracle like user
specification.
Micha
r sold as Ingres. :-)
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
rts, so I'm curious.
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
75 matches
Mail list logo
