![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Seum-Lim GAN email : slgan (AT) lucent (DOT) com | Lucent Technologies | 2000 N. Naperville Road, 6B-403F tel : (630)-713-6665 | Naperville, IL 60566, USA. fax : (630)-713-7272 | web : http://inuweb.ih.lucent.com/~slgan | +--------------------------------------------------------+ |
#2
| |||
| |||
|
|
We compiled the dyntest.pgc (in src/interfaces/ecpg/test) and tried it out but it seems like it is not able to stop after reading the last record and keep going on forever. sqlcode return is always 0 and never get to 100 where it is supposed to. The dyntest.pgc has not changed from 7.3.4 to 7.4 and it used to work in 7.3.4. |
#3
| |||
| |||
|
|
On Wed, Dec 10, 2003 at 01:50:39PM -0600, Seum-Lim Gan wrote: We compiled the dyntest.pgc (in src/interfaces/ecpg/test) and tried it out but it seems like it is not able to stop after reading the last record and keep going on forever. sqlcode return is always 0 and never get to 100 where it is supposed to. The dyntest.pgc has not changed from 7.3.4 to 7.4 and it used to work in 7.3.4. Do you use any special options to ecpg? I just tried with CVS HEAD and it runs without a problem. Albeit on an empty database just showing the system tables. Anyone else having problems with this test case? Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes (AT) jabber (DOT) org Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! |
|
Seum-Lim GAN email : slgan (AT) lucent (DOT) com | Lucent Technologies | 2000 N. Naperville Road, 6B-403F tel : (630)-713-6665 | Naperville, IL 60566, USA. fax : (630)-713-7272 | web : http://inuweb.ih.lucent.com/~slgan | +--------------------------------------------------------+ |
#4
| |||
| |||
|
|
/platdb/bin/ecpg -I /platdb/include -o dyntest74.c dyntest.pgc cc -I/platdb/include -R/platdb/lib -L/platdb/lib -lecpg -o lucyDyntest74 dyntest74.c |
#5
| |||
| |||
|
|
Hi Michael, We tried but seems this didn't solve the problem. Actually the ldd command in the log I attached yesterday has showed the link to the right libecpgtypes.so and libpg.so. |
#6
| |||
| |||
|
|
Hi, On Thu, Dec 11, 2003 at 04:10:05PM -0600, Seum-Lim Gan wrote: Hi Michael, We tried but seems this didn't solve the problem. Actually the ldd command in the log I attached yesterday has showed the link to the right libecpgtypes.so and libpg.so. You misunderstood 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 Fam-Meskes dot De ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes (AT) jabber (DOT) org 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 subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your message can get through to the mailing list cleanly |
|
Seum-Lim GAN email : slgan (AT) lucent (DOT) com | Lucent Technologies | 2000 N. Naperville Road, 6B-403F tel : (630)-713-6665 | Naperville, IL 60566, USA. fax : (630)-713-7272 | web : http://inuweb.ih.lucent.com/~slgan | +--------------------------------------------------------+ |
#7
| |||
| |||
|
|
I attach the logs here with empty database and pg_table. (I assume the empty database means we don't assign DB any value such as "mm"). The log is big since it |
|
Another thing is when I query a non-existing table, there are Errors in the log, but the the dyntest example didn't stop either. So it seems to me the sqlca.sqlcode is never set. I have also tried to print out sqlstate, it's always 00000. |
#8
| |||
| |||
|
|
I attach the logs here with empty database and pg_table. (I assume the empty database means we don't assign DB any value such as "mm"). The log is big since it |
|
Another thing is when I query a non-existing table, there are Errors in the log, but the the dyntest example didn't stop either. So it seems to me the sqlca.sqlcode is never set. I have also tried to print out sqlstate, it's always 00000. |
#9
| |||
| |||
|
|
I attach the logs here with empty database and pg_table. (I assume the empty database means we don't assign DB any value such as "mm"). The log is big since it |
|
Another thing is when I query a non-existing table, there are Errors in the log, but the the dyntest example didn't stop either. So it seems to me the sqlca.sqlcode is never set. I have also tried to print out sqlstate, it's always 00000. |
#10
| |||
| |||
|
|
Yes, the enable-thread-safety is used in configure file. Is it expected to be there? |
|
I can try an empty database and let you know the result. |
|
For machine login, I'm afraid it will be agains Lucent Security policy. Maybe we can try to open a Netmeeting session and share the desktop to see the same window. |
![]() |
| Thread Tools | |
| Display Modes | |
| |