sqlrelay-discussion Mailing List for SQL Relay (Page 39)
Brought to you by:
mused
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
(20) |
Mar
(27) |
Apr
(17) |
May
(32) |
Jun
(45) |
Jul
(49) |
Aug
(68) |
Sep
(44) |
Oct
(29) |
Nov
(64) |
Dec
(25) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(61) |
Feb
(22) |
Mar
(25) |
Apr
(31) |
May
(18) |
Jun
(28) |
Jul
(19) |
Aug
(16) |
Sep
(8) |
Oct
(17) |
Nov
(32) |
Dec
(4) |
| 2007 |
Jan
(20) |
Feb
(25) |
Mar
(5) |
Apr
(12) |
May
(11) |
Jun
(18) |
Jul
(16) |
Aug
(22) |
Sep
(37) |
Oct
(20) |
Nov
(11) |
Dec
(2) |
| 2008 |
Jan
(11) |
Feb
(33) |
Mar
(12) |
Apr
(18) |
May
(22) |
Jun
(31) |
Jul
(23) |
Aug
(6) |
Sep
|
Oct
(10) |
Nov
(22) |
Dec
|
| 2009 |
Jan
(12) |
Feb
(8) |
Mar
(11) |
Apr
(20) |
May
(18) |
Jun
(7) |
Jul
(27) |
Aug
(2) |
Sep
(10) |
Oct
(5) |
Nov
(2) |
Dec
(1) |
| 2010 |
Jan
(11) |
Feb
(18) |
Mar
(10) |
Apr
(28) |
May
(28) |
Jun
|
Jul
(27) |
Aug
(9) |
Sep
(21) |
Oct
(2) |
Nov
(2) |
Dec
(11) |
| 2011 |
Jan
|
Feb
(2) |
Mar
(4) |
Apr
(2) |
May
(2) |
Jun
(44) |
Jul
(9) |
Aug
(2) |
Sep
(12) |
Oct
(7) |
Nov
(11) |
Dec
(7) |
| 2012 |
Jan
(5) |
Feb
|
Mar
(9) |
Apr
(9) |
May
(12) |
Jun
|
Jul
(13) |
Aug
(3) |
Sep
(3) |
Oct
(1) |
Nov
(1) |
Dec
(10) |
| 2013 |
Jan
(21) |
Feb
(3) |
Mar
(4) |
Apr
|
May
(3) |
Jun
(2) |
Jul
(3) |
Aug
(3) |
Sep
(3) |
Oct
|
Nov
|
Dec
(4) |
| 2014 |
Jan
(7) |
Feb
|
Mar
(1) |
Apr
|
May
(2) |
Jun
|
Jul
(4) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Sylvain G. <S.G...@fo...> - 2006-10-12 07:45:07
|
OK, Thanks.
I do not know what I have done but it is working.
Thanks a lot for your explanation, it will help me.
Regards
_____ =20
Sylvain Gourvil
D=E9veloppeur Php/MySQL
s.g...@fo...
FOTOVISTA
43-47 avenue de la Grande Arm=E9e 75016
-----Message d'origine-----
De=A0: sql...@li... =
[mailto:sql...@li...] De la part de =
David Muse
Envoy=E9=A0: mercredi 11 octobre 2006 16:07
=C0=A0: Discussion of topics related to SQL Relay
Objet=A0: Re: [Sqlrelay-discussion] RE : Oracle : Prefetch ?
On the server side, SQL Relay's oracle connection daemon prefetches 10
rows from the database by default. You can tune this by setting the
fetchatonce connectstring parameter in sqlrelay.conf:
<instance id=3D"oracle8test" ...>
...
<connections>
<connection connectionid=3D"db"
string=3D"user=3Dtestuser;password=3Dtestpassword;oracle_home=3D/u01/app/=
oracle/product/10.2.0;oracle_sid=3Dora1:fetchatonce=3D20" metric=3D"6"/>
</connections>
</instance>
The SQL Relay client fetches all rows of the result set from the SQL
Relay server by default. To conserve RAM, you can limit the number of
rows that are fetched at once using setResultSetBufferSize. It
shouldn't limit the result set. The code you're using should work fine.
I'll run a few tests to see what's I get and let you know what I find.
David Muse
dav...@fi...
On Tue, 2006-10-10 at 16:52 +0200, Sylvain Gourvil wrote:
> =20
>=20
> I have used the example code from the sourceforge documentation.
>=20
> =20
>=20
> The result is a "limit-like".
>=20
> =20
>=20
> <?
> dl("sql_relay.so");
> =20
> $con=3Dsqlrcon_alloc("host",9000,"","user","password",0,1);
> $cur=3Dsqlrcur_alloc($con);
> =20
> sqlrcur_setResultSetBufferSize($cur,5);
> =20
> sqlrcur_sendQuery($cur,"select * from my_table");
> =20
> while (!done) {
> for ($col=3D0; $col<sqlrcur_colCount($cur); $col++) {
> if ($field=3Dsqlrcur_getField($cur,$row,$col)) {
> echo $field;
> echo ",";
> } else {
> done=3D1;
> }
> }
> echo "\n";
> $row++;
> }
>=20
> ?>
>=20
> =20
>=20
> If somebody has a good code for using buffer and prefetch with sql
> relay, could he show me ?
>=20
> =20
>=20
> Thanks.
>=20
> =20
>=20
> Regards
>=20
> =20
>=20
> =20
>=20
> -----Message d'origine-----
> De : sql...@li...
> [mailto:sql...@li...] De la part
> de Sylvain Gourvil=20
> Envoy=E9 : mardi 10 octobre 2006 15:26
> =C0 : sql...@li...
> Objet : [Sqlrelay-discussion] Oracle : Prefetch ?
>=20
> =20
>=20
> =20
>=20
> Hi everybody ?
>=20
> =20
>=20
> I am trying to put SQL Relay in a framework ans I need to deal with
> prefetch (Oracle).
>=20
> I can not find any subject about it;
>=20
> =20
>=20
> Does SQL Relay deal with prefetch?
>=20
> IF yes, could you help me?
>=20
> =20
>=20
> Thanks in advance.
>=20
> =20
>=20
> Regards.
>=20
> =20
>=20
>=20
> =
-------------------------------------------------------------------------=
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =
share your
> opinions on IT & business topics through brief surveys -- and earn =
cash
> =
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________ Sqlrelay-discussion =
mailing list Sql...@li... =
https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion
-------------------------------------------------------------------------=
Using Tomcat but need to do more? Need to support web services, =
security?
Get stuff done quickly with pre-integrated technology to make your job =
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache =
Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642
_______________________________________________
Sqlrelay-discussion mailing list
Sql...@li...
https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion
|
|
From: David M. <dav...@fi...> - 2006-10-11 14:06:59
|
On the server side, SQL Relay's oracle connection daemon prefetches 10
rows from the database by default. You can tune this by setting the
fetchatonce connectstring parameter in sqlrelay.conf:
<instance id=3D"oracle8test" ...>
...
<connections>
<connection connectionid=3D"db"
string=3D"user=3Dtestuser;password=3Dtestpassword;oracle_home=3D/u01/app/=
oracle/product/10.2.0;oracle_sid=3Dora1:fetchatonce=3D20" metric=3D"6"/>
</connections>
</instance>
The SQL Relay client fetches all rows of the result set from the SQL
Relay server by default. To conserve RAM, you can limit the number of
rows that are fetched at once using setResultSetBufferSize. It
shouldn't limit the result set. The code you're using should work fine.
I'll run a few tests to see what's I get and let you know what I find.
David Muse
dav...@fi...
On Tue, 2006-10-10 at 16:52 +0200, Sylvain Gourvil wrote:
> =20
>=20
> I have used the example code from the sourceforge documentation.
>=20
> =20
>=20
> The result is a =E2=80=9Climit-like=E2=80=9D.
>=20
> =20
>=20
> <?
> dl("sql_relay.so");
> =20
> $con=3Dsqlrcon_alloc("host",9000,"","user","password",0,1);
> $cur=3Dsqlrcur_alloc($con);
> =20
> sqlrcur_setResultSetBufferSize($cur,5);
> =20
> sqlrcur_sendQuery($cur,"select * from my_table");
> =20
> while (!done) {
> for ($col=3D0; $col<sqlrcur_colCount($cur); $col++) {
> if ($field=3Dsqlrcur_getField($cur,$row,$col)) {
> echo $field;
> echo ",";
> } else {
> done=3D1;
> }
> }
> echo "\n";
> $row++;
> }
>=20
> ?>
>=20
> =20
>=20
> If somebody has a good code for using buffer and prefetch with sql
> relay, could he show me ?
>=20
> =20
>=20
> Thanks.
>=20
> =20
>=20
> Regards
>=20
> =20
>=20
> =20
>=20
> -----Message d'origine-----
> De : sql...@li...
> [mailto:sql...@li...] De la part
> de Sylvain Gourvil=20
> Envoy=C3=A9 : mardi 10 octobre 2006 15:26
> =C3=80 : sql...@li...
> Objet : [Sqlrelay-discussion] Oracle : Prefetch ?
>=20
> =20
>=20
> =20
>=20
> Hi everybody ?
>=20
> =20
>=20
> I am trying to put SQL Relay in a framework ans I need to deal with
> prefetch (Oracle).
>=20
> I can not find any subject about it;
>=20
> =20
>=20
> Does SQL Relay deal with prefetch?
>=20
> IF yes, could you help me?
>=20
> =20
>=20
> Thanks in advance.
>=20
> =20
>=20
> Regards.
>=20
> =20
>=20
>=20
> -----------------------------------------------------------------------=
--
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share=
your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________ Sqlrelay-discussion mai=
ling list Sql...@li... https://lists.sourcef=
orge.net/lists/listinfo/sqlrelay-discussion
|
|
From: Sylvain G. <S.G...@fo...> - 2006-10-10 14:48:39
|
=20
I have used the example code from the sourceforge documentation.
=20
The result is a "limit-like".
=20
<?
dl("sql_relay.so");
=20
$con=3Dsqlrcon_alloc("host",9000,"","user","password",0,1);
$cur=3Dsqlrcur_alloc($con);
=20
sqlrcur_setResultSetBufferSize($cur,5);
=20
sqlrcur_sendQuery($cur,"select * from my_table");
=20
while (!done) {
for ($col=3D0; $col<sqlrcur_colCount($cur); $col++) {
if ($field=3Dsqlrcur_getField($cur,$row,$col)) {
echo $field;
echo ",";
} else {
done=3D1;
}
}
echo "\n";
$row++;
}
?>
=20
If somebody has a good code for using buffer and prefetch with sql =
relay, could he show me ?
=20
Thanks.
=20
Regards
=20
=20
-----Message d'origine-----
De : sql...@li... =
[mailto:sql...@li...] De la part de =
Sylvain Gourvil=20
Envoy=E9 : mardi 10 octobre 2006 15:26
=C0 : sql...@li...
Objet : [Sqlrelay-discussion] Oracle : Prefetch ?
=20
=20
Hi everybody ?
=20
I am trying to put SQL Relay in a framework ans I need to deal with =
prefetch (Oracle).
I can not find any subject about it;
=20
Does SQL Relay deal with prefetch?
IF yes, could you help me?
=20
Thanks in advance.
=20
Regards.
=20
|
|
From: Sylvain G. <S.G...@fo...> - 2006-10-10 13:34:53
|
Ok, I have found "sqlrcur_getResultSetBufferSize" and it works as I = want. It's fine. =20 But How is it possible to get the next x result in the buffer ? =20 I need some help, please ;-) =20 Regards, =20 -----Message d'origine----- De : sql...@li... = [mailto:sql...@li...] De la part de = Sylvain Gourvil=20 Envoy=E9 : mardi 10 octobre 2006 15:26 =C0 : sql...@li... Objet : [Sqlrelay-discussion] Oracle : Prefetch ? =20 =20 Hi everybody ? =20 I am trying to put SQL Relay in a framework ans I need to deal with = prefetch (Oracle). I can not find any subject about it; =20 Does SQL Relay deal with prefetch? IF yes, could you help me? =20 Thanks in advance. =20 Regards. =20 |
|
From: Sylvain G. <S.G...@fo...> - 2006-10-10 13:22:44
|
=20 Hi everybody ? =20 I am trying to put SQL Relay in a framework ans I need to deal with prefetch (Oracle). I can not find any subject about it; =20 Does SQL Relay deal with prefetch? IF yes, could you help me? =20 Thanks in advance. =20 Regards. =20 |
|
From: Thomas P. <tp...@se...> - 2006-10-02 12:17:13
|
Hello, I'm using sqlrelay 0.37 with postgresql 8.0. I have a user who searches to a specific schema : ALTER USER test_user SET search_path TO test, public; With a direct PHP connection or with psql, if I do "select * from months;" I get the test.months column. But with sqlrelay, it searches the public.months column. How can I specify the default schema (without prefixing each request with "test.") ? TIA. -- Thomas Poindessous |
|
From: <mar...@th...> - 2006-09-29 15:14:44
|
Hi=20 =20 I am trying to install sql-relay on Red Hat Linux ES4 with Oracle 9.2.0.4 support. Unfortunately I am having problems since OCI does not seem to work for this version. I think I am right in saying that you need OCI support to use SQL-RELAY to connect to an Oracle database? Also is anyone else out there having thie same problem and knows of a workaround? =20 Thanks =20 Mark |
|
From: Scooby D. <sc...@ex...> - 2006-09-27 17:56:24
|
<p>Tried upgrading to sqlrelay-0.37.1 and it appears that sqlrcur_getFieldAsLongByIndex has been removed. It is still in the website documentation and I did not see anything in the changelog or on the mailing list about it being removed.</p><p></p><p>I'm known to be blind, could someone please show me what I am missing. </p><p></p><p>Thanks,</p><p>Scooby</p> |
|
From: Marcin M. <M.M...@ne...> - 2006-09-26 13:11:07
|
Hi, I have a latest sqlrelay sources and I'm trying to build rpm packages from .spec file included in .tar.gz Compilations goes fine up to this moment: g++ -O2 -g -Wall -pipe -pthread -I./ -I../../../ -I../../../src/common -I../../../src/util -I../../../src/connection -pthread -I/usr/kerberos/include -I/usr/include/mysql -g -pipe -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I../../../src/api/c++/include -c main.C -o main.o >/dev/null 2>&1 /bin/sh ../../../libtool --mode=link g++ -o sqlr-connection-mysql mysqlconnection.lo main.lo -L/usr/lib64/mysql -lmysqlclient -lz -lcrypt -lnsl -lm -L/usr/lib64 -lssl -lcrypto -L../../../src/connection -lsqlrconnection -L../../../src/util -lsqlrutil -lrudiments -lpthread -L/usr/kerberos/lib -L/usr/kerberos/lib64 -lssl -lcrypto -lgssapi_krb5 -lkrb5 -lcom_err -lk5crypto -lresolv -ldl -lz -lrt -lrt -lcrypt -ldl -L../../../src/api/c++/src -lsqlrclient libtool: link: cannot find the library `/usr/lib64/libsqlrclient.la' make[3]: *** [sqlr-connection-mysql] Error 1 I have on this serwer already installed older versions of sqlrelay packages. Might this be the problem? If yes is there a way to solve this without uninstalling older packages? br Marcin -- http://www.actus.org.pl/ - :::: - nic-hdl: MM3380-RIPE GnuPG 6687 E661 98B0 AEE6 DA8B 7F48 AEE4 776F 5688 DC89 http://www.poznan.linux.org.pl/ : http://www.netsync.pl/ |
|
From: Jacob H. <jh...@ny...> - 2006-09-19 15:45:51
|
Hello, I'm just curious if anybody has considering adding memcached support to SqlRelay as an alternative caching mechanism. It seems like it might make a good single point of caching if you were to talk to multiple languages on the front end. Memcached servers could be specified within the Sqlrelay.conf as well. If you've been working on something like this, let's chat. Thanks! Jake |
|
From: armand\.bastien <arm...@la...> - 2006-09-18 15:15:52
|
Hi, I am trying SQLRelay 0.37 for a php site (with oracle base on a Solaris). It works greats (page displays quite faster, db load is decreased). For a test page, Php stops with a seg fault (in libsqlrclient). In this page, I have two queries that use more than 15 Column (select * with 17 columns in the table and Select C1,...,C19). If only one query is executed, there is no problem. If I compile again the php api with OPTIMISTIC_COLUMN_COUNT set to 20. The seg fault does not occur. (both queries are executed) Here is the backtrace extracted from the core file : libsqlrclient-0.37.so.1`_ZN3row8addFieldEjPKcj+0x28(1eadf8, 7800, 7800, 31, 0, fea3ee28) libsqlrclient-0.37.so.1`_ZN10sqlrcursor16processResultSetEby+0xf8(1, 0, 0, 31, 1f2628, 32) libsqlrclient-0.37.so.1`_ZN10sqlrcursor8runQueryEPKc+0x88(1, 1575c0, 1575c0, 4, 21, 0) libsqlrclient-0.37.so.1`_ZN10sqlrcursor12executeQueryEv+0x50(1eadf8, 1eadf8, c5, 1, 19, 0) libsqlrclient-0.37.so.1`_ZN10sqlrcursor9sendQueryEPKc+0x10(1eadf8, c22f8, 4632c8, 0, 1, 19) sql_relay.so`zif_sqlrcur_sendquery+0xb8(4632c8, 4670f0, 0, 1, feb364f4, 0) libphp4.so`execute+0x20fc(3b8a78, ffbe2d74, 10e6bc, 10e6c8, fee3d2f8, ffbe3b58) libphp4.so`execute+0x1e80(a18a8, ffbe3bf4, 10e6ac, ffbe3b54, fee3d2f8, ffbe4458) libphp4.so`execute+0x1e80(34c940, ffbe44f4, 1e00, 10e69c, fee3d2f8, ffbec1b8) libphp4.so`execute+0x1e80(216020, ffbec254, fee3d2f8, ffbec3a0, 28a8, 28ac) libphp4.so`execute+0x3424(2c2f68, ffbec494, fee3d2f8, ffbecb00, 0, 0) libphp4.so`execute+0x3424(334728, ffbed654, fee3d2f8, ffbee520, 0, 0) libphp4.so`execute+0x3424(3138b0, ffbee794, fee3d2f8, ffbeeae0, 0, 0) libphp4.so`execute+0x3424(3c45d8, ffbeebd4, ffbeec7c, 220c, 0, 0) libphp4.so`zend_execute_scripts+0xa8(8, 0, 3, ffbef230, fee3d0c8, ffbeece8) libphp4.so`php_execute_script+0x1f0(0, fee3a078, 99040, fffffd1c, 0, ff1bf781) libphp4.so`apache_php_module_main+0x1cc(ffffffff, 0, 0, ffffff64, ffffff6c, 22d58) libphp4.so`send_php+0x1e8(fee3d408, 0, 0, 0, 70, 70) libhttpd.so`ap_invoke_handler+0x1b0(98390, 12, 1, ff38ee3c, 231f8, fffff2b4) libhttpd.so`process_request_internal+0x150(0, 1, 98390, fee50000, 0, fffffb50) libhttpd.so`ap_process_request+0x30(98390, 2, 98390, fffff810, ff38eff0, 2) libhttpd.so`child_main+0x950(fffff204, b400, ff38b7e4, ff38b7e0, fffff09c, fffff8e8) libhttpd.so`make_child+0x11c(22d58, 2, 450e9d4e, ff385764, 0, fee50030) libhttpd.so`perform_idle_server_maintenance+0x1f4(5, 4, 450e9d4e, ff38b7a8, 5, 5) libhttpd.so`standalone_main+0x848(fffff210, fffff67c, fffff9e8, fffff700, ff38f00c, ff38ee70) libhttpd.so`ap_main+0x440(5, ffbef8a4, ffbef8bc, 20a38, 0, 0) _start+0x5c(0, 0, 0, 0, 0, 0) Take Care.=0A=0AAcc=E9dez au courrier =E9lectronique de La Poste sur www.laposte.net ou sur 3615 LAPOSTENET (0,34=80 TTC /mn) 1 Giga de stockage gratuit =96 Antispam et antivirus int=E9gr=E9s =0A |
|
From: Csaba S. <se...@ya...> - 2006-09-15 09:36:42
|
Hello, There is a bug in the MySQL autocommit future detection (acsite.m4) and in the drop in MySQL API replacement mysql_autocommit() function. $ LD_PRELOAD=/usr/lib/libmysql50sqlrelay.so perl perl_test.pl DBD driver has not implemented the AutoCommit attribute at /usr/lib/perl5/vendor_perl/5.8.8/i586-linux-thread-multi/DBI.pm line 664. Attached a patch to fix this issue. Please apply to the next release if possible. Thanks, Csaba __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Jacob H. <jh...@ny...> - 2006-09-14 18:05:37
|
Hello,
I know you're working on prerelease2, but I'm wondering if I could
request a few minor changes. I'm working on writing a custom
"database" connection for sqlrelay to interface with a daemon we have
that can take queries and return results. When compiling my change, I
found a few issues with sqlrelay I'd like to see changed if possible.
Thanks!
* One problem I had was that the code I was linking to had an enum
named DEFAULT_PORT which created a namespace collision with
SqlRelay's DEFAULT_PORT #define. I was wondering if we could rename
SqlRelay's internal defaults to start with SQLR_ to avoid such
namespace collisions in the future.
* One other thing. In my case, it's really useful for me to get the
constr as a single const char * rather than parsed into chunks. Could
we add a function
const char *sqlrconnection_svr::connectString()
that returns the whole string? Thank you.
Anyhow, those are my humble requests. Let me know if there is an
issue, but I think they should be self-explanatory. Thank you.
Jake
|
|
From: Michael R. <m.r...@fr...> - 2006-09-04 13:13:44
|
Hi everyone, i have tried to compile the rudiment sources several times by now. Everything works fine execpt rudiment did not compile the xmldom, xmldomnode and xmlsax sources at all. I dont know where to look for some hints to solve this problem. I have no problems on Linux but on my FreeBSD System the xml* sources are left out. Sqlrelay is complaining about undefined references to all the xml Classes which are needed to read the config file. So my question is how to tell rudiment to compile everything? Thanks for hints and help! Michael -- |
|
From: Ionut C. <ion...@av...> - 2006-08-29 13:17:41
|
That package only contains the php API. It normally should depend on the sqlrelay package. If it doesn't, it's probably a broken dependency. Anyway, you need to install the sqlrelay package, and if you want to run the daemon on that machine, one or more of sqlrelay-postgresql / -mysql etc. If you need the oracle daemon, you're bound to compile it from sources. php-config is missing because you didn't install php5-dev. Ionut ----- Original Message ----- From: "Marek" <ma...@da...> To: <sql...@li...> Sent: Tuesday, August 29, 2006 2:56 PM Subject: [Sqlrelay-discussion] sql_relay.so from php5-sqlrelay package | Hello Everybody, | | I used to use sqlrelay before, and would need it again for some of our | growing projects. | I installed this package: | http://packages.debian.org/unstable/misc/php5-sqlrelay | | but realized, that it only contains the changelog files, but could not find | anywhere the sql_relay.so library. | | I am using sql_relay v. 1.37-1, PHP5. I tried to compile it from the | sqlrelay sources, but it fails always due to missing php-config file which | is not included in the Debian PHP distribution. | | Can anyone advise me where to get sql_relay.so file ? | | Thank you. | | Marek | | | | ------------------------------------------------------------------------- | Using Tomcat but need to do more? Need to support web services, security? | Get stuff done quickly with pre-integrated technology to make your job easier | Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo | http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 | _______________________________________________ | Sqlrelay-discussion mailing list | Sql...@li... | https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion |
|
From: Marek <ma...@da...> - 2006-08-29 11:56:24
|
Hello Everybody, I used to use sqlrelay before, and would need it again for some of our growing projects. I installed this package: http://packages.debian.org/unstable/misc/php5-sqlrelay but realized, that it only contains the changelog files, but could not find anywhere the sql_relay.so library. I am using sql_relay v. 1.37-1, PHP5. I tried to compile it from the sqlrelay sources, but it fails always due to missing php-config file which is not included in the Debian PHP distribution. Can anyone advise me where to get sql_relay.so file ? Thank you. Marek |
|
From: Stephen C. <st...@to...> - 2006-08-24 03:13:10
|
I've been reviewing the sqltrace logs and I thinks this may be a case
where safe signals are biting me in the butt.
-> prepare for DBD::SQLRelay::db (DBI::db=HASH(0x8e05078)~0x8de04f4
'select a.statid, b.webstatdesc, a.pendid, c.penddesc,
a.certno, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
where a.statid = b.statid
and a.pendid = c.pendid (+)
and tranid = 1
and certno = ?') thr#882a008
1 <> FETCH= ( SQLRelay::Connection=SCALAR(0x8dfff7c) ) [1 items]
('driver_connection' from cache) at SQLRelay.pm line 138
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8deb994)~0x8de03a4
'driver_database_handle' DBI::db=HASH(0x8de04f4)) thr#882a008
<- STORE= 1 at SQLRelay.pm line 145
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8deb994)~0x8de03a4
'NUM_OF_PARAMS' 1) thr#882a008
<- STORE= 1 at SQLRelay.pm line 146
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8deb994)~0x8de03a4
'driver_is_select' 1) thr#882a008
<- STORE= 1 at SQLRelay.pm line 147
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8deb994)~0x8de03a4
'driver_cursor' SQLRelay::Cursor=SCALAR(0x8dfc800)) thr#882a008
<- STORE= 1 at SQLRelay.pm line 148
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8deb994)~0x8de03a4
'NUM_OF_PARAMS' 1) thr#882a008
<- STORE= 1 at SQLRelay.pm line 158
<- prepare= DBI::st=HASH(0x8deb994) at sql.pm line 164
-------------------------------------
-> execute for DBD::SQLRelay::st (DBI::st=HASH(0x8deb994)~0x8de03a4
'29721783') thr#882a008
-------------------------------------
1 <> FETCH= SQLRelay::Cursor=SCALAR(0x8dfc800) ('driver_cursor' from
cache) at SQLRelay.pm line 349
1 <> FETCH= SQLRelay::Cursor=SCALAR(0x8dfc800) ('driver_cursor' from
cache) at SQLRelay.pm line 275
-> $DBI::errstr (&) FETCH from lasth=HASH
>> DBD::SQLRelay::st::errstr
<- $DBI::errstr= undef
-> DESTROY for DBD::SQLRelay::st (DBI::st=HASH(0x8de03a4)~INNER)
thr#882a008
<- DESTROY= undef at xml-queue.pl line 309
Here I request the status for certno = 29721783. However the alarm was
triggered (18 second time out BTW!) and I 'timed out" the call and
undef'ed the script handle. However I suspect the signal was not
delivered until the execute completed. Leading me to the next invocation:
-> prepare for DBD::SQLRelay::db (DBI::db=HASH(0x8e05078)~0x8de04f4
'select a.statid, b.webstatdesc, a.pendid, c.penddesc,
a.certno, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
where a.statid = b.statid
and a.pendid = c.pendid (+)
and tranid = 1
and certno = ?') thr#882a008
1 <> FETCH= ( SQLRelay::Connection=SCALAR(0x8dfff7c) ) [1 items]
('driver_connection' from cache) at SQLRelay.pm line 138
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8dd7f10)~0x8dd9180
'driver_database_handle' DBI::db=HASH(0x8de04f4)) thr#882a008
<- STORE= 1 at SQLRelay.pm line 145
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8dd7f10)~0x8dd9180
'NUM_OF_PARAMS' 1) thr#882a008
<- STORE= 1 at SQLRelay.pm line 146
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8dd7f10)~0x8dd9180
'driver_is_select' 1) thr#882a008
<- STORE= 1 at SQLRelay.pm line 147
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8dd7f10)~0x8dd9180
'driver_cursor' SQLRelay::Cursor=SCALAR(0x8e4d628)) thr#882a008
<- STORE= 1 at SQLRelay.pm line 148
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8dd7f10)~0x8dd9180
'NUM_OF_PARAMS' 1) thr#882a008
<- STORE= 1 at SQLRelay.pm line 158
<- prepare= DBI::st=HASH(0x8dd7f10) at sql.pm line 164
----------------------------------------------
-> execute for DBD::SQLRelay::st (DBI::st=HASH(0x8dd7f10)~0x8dd9180
'28888521') thr#882a008
----------------------------------------------
1 <> FETCH= SQLRelay::Cursor=SCALAR(0x8e4d628) ('driver_cursor' from
cache) at SQLRelay.pm line 349
1 <> FETCH= SQLRelay::Cursor=SCALAR(0x8e4d628) ('driver_cursor' from
cache) at SQLRelay.pm line 275
1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0x8dd9180)~INNER
'NUM_OF_FIELDS') thr#882a008
1 <- FETCH= undef at SQLRelay.pm line 379
1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8dd9180)~INNER
'NUM_OF_FIELDS' 6) thr#882a008
1 <- STORE= 1 at SQLRelay.pm line 379
1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8dd9180)~INNER
'driver_FETCHED_ROWS' 0) thr#882a008
1 <- STORE= 1 at SQLRelay.pm line 384
1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0x8dd9180)~INNER
'driver_param_inout_list') thr#882a008
1 <- FETCH= undef at SQLRelay.pm line 387
1 -> rows for DBD::SQLRelay::st (DBI::st=HASH(0x8dd9180)~INNER)
thr#882a008
2 <> FETCH= SQLRelay::Cursor=SCALAR(0x8e4d628) ('driver_cursor' from
cache) at SQLRelay.pm line 446
1 <- rows= 0 at SQLRelay.pm line 399
<- execute= '0E0' at sql.pm line 212
-> fetchrow_arrayref for DBD::SQLRelay::st
(DBI::st=HASH(0x8dd7f10)~0x8dd9180) thr#882a008
1 <> FETCH= 0 ('driver_FETCHED_ROWS' from cache) at SQLRelay.pm line 412
1 <> FETCH= SQLRelay::Cursor=SCALAR(0x8e4d628) ('driver_cursor' from
cache) at SQLRelay.pm line 422
1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x8dd9180)~INNER
'driver_FETCHED_ROWS' 1) thr#882a008
1 <- STORE= 1 at SQLRelay.pm line 426
1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0x8dd9180)~INNER
'ChopBlanks') thr#882a008
1 <- FETCH= '' at SQLRelay.pm line 429
------------------------
<- fetchrow_arrayref= [ '9' 'Pending' '3' 'Waiting for info from
Client' '29721783' '08-23-2006 11:25:12' ] row1 at sql.pm line 233
------------------------
-> fetchrow_arrayref for DBD::SQLRelay::st
(DBI::st=HASH(0x8dd7f10)~0x8dd9180) thr#882a008
1 <> FETCH= 1 ('driver_FETCHED_ROWS' from cache) at SQLRelay.pm line 412
1 <> FETCH= SQLRelay::Cursor=SCALAR(0x8e4d628) ('driver_cursor' from
cache) at SQLRelay.pm line 422
<- fetchrow_arrayref= undef row1 at sql.pm line 242
-> DESTROY for DBD::SQLRelay::st (DBI::st=HASH(0x8dd9180)~INNER)
thr#882a008
<- DESTROY= undef at xml-queue.pl line 309
This time DBI/SQLRelay returned the results from the previous call
(certno = 29721783) instead of the present one (certno = 28888521) and,
I guess only believing there was one row returned, held the actual
result in a buffer somewhere. Every subsequent call up until I
disconnect shows this one row off behavior. Then things reset and I'm
OK until the the next time a script takes too long to execute.
David Muse wrote:
> Interesting. Could you send me an example of the code that doesn't work
> and the fix? I'd like to take a closer look and see what's going on.
>
> Dave
>
> On Sun, 2006-08-13 at 08:58 -0700, Stephen Carville wrote:
>
>>I found that if I undef the script handle after each execution, things
>>seem to work OK. If you use bind variables, Oracle will cache the
>>compiled script so the impact of a prepare() before each execute is small.
>>
>>-------- Original Message --------
>>Subject: Show Stopper?
>>Date: Thu, 19 Aug 2006 13:39:22 -0700
>>From: Stephen Carville <st...@to...>
>>To: SQlRelay List <sql...@li...>
>>
>>I've been using sqlrelay 0.37 with oracle8 connector, Perl 5.8.x and
>>Oracle 10g for about two weeks now and I've noticed an ocassional case
>>where the data returned did not seem right. This was intermittent and
>>rare -- maybe one or two every thousand order -- but finally a
>>test case proved to me sqlrelay doesn't always return the correct data.
>>
>>I sent the follwing SQL:
>>select a.statid, b.webstatdesc, a.pendid, c.penddesc,
>>a.certno, a.reqid, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
>>from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
>>where a.statid = b.statid
>>and a.pendid = c.pendid (+)
>>and tranid = 1
>>and certno = 29693421
>>
>>I got back
>>
>> '7' 'Completed' undef undef '29752604' '28168039' '08-10-2006 11:13:08'
>>
>>The correct values s/b:
>>
>> '9' 'Pending' '3' 'Waiting for info from Client' '29693421' '28109417'
>>'08-10-2006 11:13:08'
>>
>>Notice the difference in the 'certno' and 'reqid' fields. These _never_
>>change once an order has been submitted. At first I assumed the orders
>>were being marked completed in error but as the above shows it is the
>>data returned that is sometimes wrong.
>>
>>Here is the results from the DBI trace log:
>>
>> -> prepare for DBD::SQLRelay::db (DBI::db=HASH(0xa2d42f8)~0xa33a29c
>>'select
>>a.statid, b.webstatdesc, a.pendid, c.penddesc,
>>a.certno, a.reqid, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
>>from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
>>where a.statid = b.statid
>>and a.pendid = c.pendid (+)
>>and tranid = 1
>>and certno = 29693421') thr#9d30008
>>1 <- FETCH= ( SQLRelay::Connection=SCALAR(0xa33a410) ) [1 items]
>>('driver_connection' from cache) at SQLRelay.pm line 138
>> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
>>'driver_database_handle' DBI::db=HASH(0xa33a29c)) thr#9d30008
>> <- STORE= 1 at SQLRelay.pm line 145
>> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
>>'NUM_OF_PARAMS' 0) thr#9d30008
>> <- STORE= 1 at SQLRelay.pm line 146
>> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
>>'driver_is_select' 1) thr#9d30008
>> <- STORE= 1 at SQLRelay.pm line 147
>> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
>>'driver_cursor' SQLRelay::Cursor=SCALAR(0xa2c77dc)) thr#9d30008
>> <- STORE= 1 at SQLRelay.pm line 148
>> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
>>'NUM_OF_PARAMS' 0) thr#9d30008
>> <- STORE= 1 at SQLRelay.pm line 158
>> <- prepare= DBI::st=HASH(0x9d49a84) at sql.pm line 223
>> -> execute for DBD::SQLRelay::st
>>(DBI::st=HASH(0x9d49a84)~0xa2c774c) thr#9d30008
>>1 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
>>cache) at SQLRelay.pm line 349
>>1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'NUM_OF_FIELDS') thr#9d30008
>>1 <- FETCH= 0 at SQLRelay.pm line 379
>>1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'NUM_OF_FIELDS' 7) thr#9d30008
>>1 <- STORE= 1 at SQLRelay.pm line 379
>>1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'driver_FETCHED_ROWS' 0) thr#9d30008
>>1 <- STORE= 1 at SQLRelay.pm line 384
>>1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'driver_param_inout_list') thr#9d30008
>>1 <- FETCH= undef at SQLRelay.pm line 387
>>1 -> rows for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER)
>>thr#9d30008
>>2 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
>>cache) at SQLRelay.pm line 446
>>1 <- rows= 0 at SQLRelay.pm line 399
>> <- execute= '0E0' at sql.pm line 230
>> -> fetchrow_arrayref for DBD::SQLRelay::st
>>(DBI::st=HASH(0x9d49a84)~0xa2c774c) thr#9d30008
>>1 <- FETCH= 0 ('driver_FETCHED_ROWS' from cache) at SQLRelay.pm line 412
>>1 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
>>cache) at SQLRelay.pm line 422
>>1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'driver_FETCHED_ROWS' 1) thr#9d30008
>>1 <- STORE= 1 at SQLRelay.pm line 426
>>1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'ChopBlanks')thr#9d30008
>>1 <- FETCH= '' at SQLRelay.pm line 429
>> <- fetchrow_arrayref= [ '7' 'Completed' undef undef '29752604'
>>'28168039' '08-10-2006 11:13:08' ] row1 at sql.pm line 255
>>
>>I have several other requests with similar errors.
>>
>>--
>>Stephen Carville <st...@to...>
>>Unix and Network Admin
>>Nationwide Totalflood
>>6033 W. Century Blvd
>>Los Angeles, CA 90045
>>310-342-3602
>>
>>
>>
>
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Sqlrelay-discussion mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion
--
Stephen Carville <st...@to...>
Unix and Network Admin
Nationwide Totalflood
6033 W. Century Blvd
Los Angeles, CA 90045
310-342-3602
|
|
From: Stephen C. <st...@to...> - 2006-08-16 04:18:21
|
David Muse wrote:
> Interesting. Could you send me an example of the code that doesn't work
> and the fix? I'd like to take a closer look and see what's going on.
The following code works. If I remove the line
undef $sth if ($sth);
it will begin generating the errors again.
from xmlcommon.pm:
{ my ($sth);
sub xml_getstatus_by_certno {
my ($certno) = @_;
my ($status,$line,$timeout);
my (%results);
my $SCRIPT = "select a.statid, b.webstatdesc, a.pendid, c.penddesc,
a.certno, a.reqid, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
where a.statid = b.statid
and a.pendid = c.pendid (+)
and tranid = 1
and certno = ?";
unless ($sth) {
$timeout = log_get_timeout();
$sth = edi_prepare_sql($SCRIPT,$timeout);
}
$timeout = log_get_timeout();
%results = edi_run_select($sth,$timeout,$certno);
undef $sth if ($sth);
$line = edi_get_last_results() . "\n";
log_db_addlines($line);
# get the status code and message
return evaluate_status(%results);
}
}
From sql.pm:
use DBI;
use Sys::SigAction qw (set_sig_handler);
# prepare a script for execution
#
sub edi_prepare_sql {
my($script,$timeout) = @_;
my ($sth);
$edi_lastresult = "";
$timeout = $EDI_TIMEOUT unless ($timeout);
unless ($edi_dbh) {
$edi_lastresult = "connection to DB lost";
return 0;
}
eval {
my $h = set_sig_handler('ALRM',
sub {$sth = 0; die;},
{ mask=>[qw(INT ALRM)],safe =>
$edi_safe_signal });
# set alarm
alarm($timeout);
# prepare the script
$sth = $edi_dbh->prepare($script);
# reset alarm
alarm(0);
};
# reset alarm JIC
alarm(0);
if ($@) {
$edi_lastresult = DBI::errstr;
}
unless ($sth) {
$edi_lastresult =
"Prepared timed out in $timeout seconds" unless ($edi_lastresult);
}
return $sth;
}
# executre a SELECT statement
#
sub edi_run_select {
my($sth,$timeout,@bind_vars) = @_;
my ($rv,$val,$cntr,$row);
my (%tbl);
$tbl{0}[0] = "ERROR";
$tbl{1}[0] = "noservice";
$edi_lastresult = "";
$timeout = $EDI_TIMEOUT unless ($timeout);
# if handle is not there
unless ($sth) {
$edi_lastresult = "cannot execute (connection lost?)";
return %tbl;
}
eval {
my $h = set_sig_handler('ALRM',
sub {$rv = 0; die;},
{ mask=>[qw(INT ALRM)],safe =>
$edi_safe_signal });
# set alarm
alarm($timeout);
# execute the script
$rv = $sth->execute(@bind_vars);
# reset alarm on success
alarm(0);
};
# reset alarm JIC
alarm(0);
# if execute failed
if ($@) {
$edi_lastresult = DBI::errstr;
return %tbl;
}
unless ($rv) {
$edi_lastresult = ($edi_lastresult ||"Select timed out in $timeout
seconds:"
);
return %tbl;
}
$cntr = 0;
# no headers yet...
$tbl{0}[0] = "SUCCESS";
$tbl{1} = ();
while ($row = $sth->fetchrow_arrayref) {
$cntr++;
foreach (@$row) {
$val = (trim($_) || "");
push @{$tbl{$cntr}},$val;
$edi_lastresult .= ($val || "undef") . "\t";
}
# sorta tabular format
chop $edi_lastresult;
$edi_lastresult .= "\n";
}
# if no rows -- no rows returned is not always an error
unless ($cntr) {
$edi_lastresult = "no rows returned";
$tbl{1}[0] = "no rows";
}
return %tbl;
}
> Dave
>
> On Sun, 2006-08-13 at 08:58 -0700, Stephen Carville wrote:
>
>>I found that if I undef the script handle after each execution, things
>>seem to work OK. If you use bind variables, Oracle will cache the
>>compiled script so the impact of a prepare() before each execute is small.
>>
>>-------- Original Message --------
>>Subject: Show Stopper?
>>Date: Thu, 19 Aug 2006 13:39:22 -0700
>>From: Stephen Carville <st...@to...>
>>To: SQlRelay List <sql...@li...>
>>
>>I've been using sqlrelay 0.37 with oracle8 connector, Perl 5.8.x and
>>Oracle 10g for about two weeks now and I've noticed an ocassional case
>>where the data returned did not seem right. This was intermittent and
>>rare -- maybe one or two every thousand order -- but finally a
>>test case proved to me sqlrelay doesn't always return the correct data.
>>
>>I sent the follwing SQL:
>>select a.statid, b.webstatdesc, a.pendid, c.penddesc,
>>a.certno, a.reqid, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
>>from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
>>where a.statid = b.statid
>>and a.pendid = c.pendid (+)
>>and tranid = 1
>>and certno = 29693421
>>
>>I got back
>>
>> '7' 'Completed' undef undef '29752604' '28168039' '08-10-2006 11:13:08'
>>
>>The correct values s/b:
>>
>> '9' 'Pending' '3' 'Waiting for info from Client' '29693421' '28109417'
>>'08-10-2006 11:13:08'
>>
>>Notice the difference in the 'certno' and 'reqid' fields. These _never_
>>change once an order has been submitted. At first I assumed the orders
>>were being marked completed in error but as the above shows it is the
>>data returned that is sometimes wrong.
>>
>>Here is the results from the DBI trace log:
>>
>> -> prepare for DBD::SQLRelay::db (DBI::db=HASH(0xa2d42f8)~0xa33a29c
>>'select
>>a.statid, b.webstatdesc, a.pendid, c.penddesc,
>>a.certno, a.reqid, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
>>from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
>>where a.statid = b.statid
>>and a.pendid = c.pendid (+)
>>and tranid = 1
>>and certno = 29693421') thr#9d30008
>>1 <- FETCH= ( SQLRelay::Connection=SCALAR(0xa33a410) ) [1 items]
>>('driver_connection' from cache) at SQLRelay.pm line 138
>> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
>>'driver_database_handle' DBI::db=HASH(0xa33a29c)) thr#9d30008
>> <- STORE= 1 at SQLRelay.pm line 145
>> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
>>'NUM_OF_PARAMS' 0) thr#9d30008
>> <- STORE= 1 at SQLRelay.pm line 146
>> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
>>'driver_is_select' 1) thr#9d30008
>> <- STORE= 1 at SQLRelay.pm line 147
>> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
>>'driver_cursor' SQLRelay::Cursor=SCALAR(0xa2c77dc)) thr#9d30008
>> <- STORE= 1 at SQLRelay.pm line 148
>> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
>>'NUM_OF_PARAMS' 0) thr#9d30008
>> <- STORE= 1 at SQLRelay.pm line 158
>> <- prepare= DBI::st=HASH(0x9d49a84) at sql.pm line 223
>> -> execute for DBD::SQLRelay::st
>>(DBI::st=HASH(0x9d49a84)~0xa2c774c) thr#9d30008
>>1 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
>>cache) at SQLRelay.pm line 349
>>1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'NUM_OF_FIELDS') thr#9d30008
>>1 <- FETCH= 0 at SQLRelay.pm line 379
>>1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'NUM_OF_FIELDS' 7) thr#9d30008
>>1 <- STORE= 1 at SQLRelay.pm line 379
>>1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'driver_FETCHED_ROWS' 0) thr#9d30008
>>1 <- STORE= 1 at SQLRelay.pm line 384
>>1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'driver_param_inout_list') thr#9d30008
>>1 <- FETCH= undef at SQLRelay.pm line 387
>>1 -> rows for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER)
>>thr#9d30008
>>2 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
>>cache) at SQLRelay.pm line 446
>>1 <- rows= 0 at SQLRelay.pm line 399
>> <- execute= '0E0' at sql.pm line 230
>> -> fetchrow_arrayref for DBD::SQLRelay::st
>>(DBI::st=HASH(0x9d49a84)~0xa2c774c) thr#9d30008
>>1 <- FETCH= 0 ('driver_FETCHED_ROWS' from cache) at SQLRelay.pm line 412
>>1 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
>>cache) at SQLRelay.pm line 422
>>1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'driver_FETCHED_ROWS' 1) thr#9d30008
>>1 <- STORE= 1 at SQLRelay.pm line 426
>>1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
>>'ChopBlanks')thr#9d30008
>>1 <- FETCH= '' at SQLRelay.pm line 429
>> <- fetchrow_arrayref= [ '7' 'Completed' undef undef '29752604'
>>'28168039' '08-10-2006 11:13:08' ] row1 at sql.pm line 255
>>
>>I have several other requests with similar errors.
>>
>>--
>>Stephen Carville <st...@to...>
>>Unix and Network Admin
>>Nationwide Totalflood
>>6033 W. Century Blvd
>>Los Angeles, CA 90045
>>310-342-3602
>>
>>
>>
>
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Sqlrelay-discussion mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion
--
Stephen Carville <st...@to...>
Unix and Network Admin
Nationwide Totalflood
6033 W. Century Blvd
Los Angeles, CA 90045
310-342-3602
|
|
From: David M. <dav...@fi...> - 2006-08-15 02:30:57
|
Aaah, just noticed this message in my crowded inbox.
It's tricky for SQL Relay to report anything but DB_ERROR. The Pear DB
driver would have to parse all of the possible error strings that SQL
Relay can return and set the proper code for each. A good solution
would be for SQL Relay to define a set of error codes and have each SQL
Relay connection translate the database error codes to SQL Relay's
codes, and return the SQL Relay error code in addition to the native
code and string. Then the Pear DB driver could translate the SQL Relay
error code to a Pear DB error code.
It'd be a bit of work to do that though, it probably won't be in the
next release :)
In the mean time, the error string should be in there, the Pear DB
driver calls:
$error = sqlrcur_errorMessage($sqlrcursor->cursor);
return $this->raiseError(DB_ERROR, null, null, null,
$error);
whenever an error occurs so your app could potentially parse it, though
that's not a great solution.
Dave
dav...@fi...
On Tue, 2006-08-01 at 22:29 -0400, Dave Sugar wrote:
> Hi,
>
> I have been doing some repurposing of some PHP code to use SQLRelay
> instead of the PEAR oci8 interface. And all is generally pretty
> good, but I have noticed some cases were we are checking for specific
> error conditions returned from the database and those conditions are
> not being met when using SQLRelay.
>
> An example of this is a case where we perform an insert and expect
> that we might get back the error DB_ERROR_ALREADY_EXISTS if the
> insert fails because the row already exists. But SQLRelay doesn't
> seem to care what the error is, it just returns the generic error
> DB_ERROR. Is there a way to get SQLRelay to know more information
> about the error that has been returned?
>
> We are using SQLRelay 0.37 which I believe is the latest.
>
> Thanks
> Dave Sugar
> dsu...@co...
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sqlrelay-discussion mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion
>
|
|
From: David M. <dav...@fi...> - 2006-08-15 02:10:20
|
Interesting. Could you send me an example of the code that doesn't work
and the fix? I'd like to take a closer look and see what's going on.
Dave
On Sun, 2006-08-13 at 08:58 -0700, Stephen Carville wrote:
> I found that if I undef the script handle after each execution, things
> seem to work OK. If you use bind variables, Oracle will cache the
> compiled script so the impact of a prepare() before each execute is small.
>
> -------- Original Message --------
> Subject: Show Stopper?
> Date: Thu, 19 Aug 2006 13:39:22 -0700
> From: Stephen Carville <st...@to...>
> To: SQlRelay List <sql...@li...>
>
> I've been using sqlrelay 0.37 with oracle8 connector, Perl 5.8.x and
> Oracle 10g for about two weeks now and I've noticed an ocassional case
> where the data returned did not seem right. This was intermittent and
> rare -- maybe one or two every thousand order -- but finally a
> test case proved to me sqlrelay doesn't always return the correct data.
>
> I sent the follwing SQL:
> select a.statid, b.webstatdesc, a.pendid, c.penddesc,
> a.certno, a.reqid, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
> from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
> where a.statid = b.statid
> and a.pendid = c.pendid (+)
> and tranid = 1
> and certno = 29693421
>
> I got back
>
> '7' 'Completed' undef undef '29752604' '28168039' '08-10-2006 11:13:08'
>
> The correct values s/b:
>
> '9' 'Pending' '3' 'Waiting for info from Client' '29693421' '28109417'
> '08-10-2006 11:13:08'
>
> Notice the difference in the 'certno' and 'reqid' fields. These _never_
> change once an order has been submitted. At first I assumed the orders
> were being marked completed in error but as the above shows it is the
> data returned that is sometimes wrong.
>
> Here is the results from the DBI trace log:
>
> -> prepare for DBD::SQLRelay::db (DBI::db=HASH(0xa2d42f8)~0xa33a29c
> 'select
> a.statid, b.webstatdesc, a.pendid, c.penddesc,
> a.certno, a.reqid, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
> from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
> where a.statid = b.statid
> and a.pendid = c.pendid (+)
> and tranid = 1
> and certno = 29693421') thr#9d30008
> 1 <- FETCH= ( SQLRelay::Connection=SCALAR(0xa33a410) ) [1 items]
> ('driver_connection' from cache) at SQLRelay.pm line 138
> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
> 'driver_database_handle' DBI::db=HASH(0xa33a29c)) thr#9d30008
> <- STORE= 1 at SQLRelay.pm line 145
> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
> 'NUM_OF_PARAMS' 0) thr#9d30008
> <- STORE= 1 at SQLRelay.pm line 146
> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
> 'driver_is_select' 1) thr#9d30008
> <- STORE= 1 at SQLRelay.pm line 147
> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
> 'driver_cursor' SQLRelay::Cursor=SCALAR(0xa2c77dc)) thr#9d30008
> <- STORE= 1 at SQLRelay.pm line 148
> -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
> 'NUM_OF_PARAMS' 0) thr#9d30008
> <- STORE= 1 at SQLRelay.pm line 158
> <- prepare= DBI::st=HASH(0x9d49a84) at sql.pm line 223
> -> execute for DBD::SQLRelay::st
> (DBI::st=HASH(0x9d49a84)~0xa2c774c) thr#9d30008
> 1 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
> cache) at SQLRelay.pm line 349
> 1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
> 'NUM_OF_FIELDS') thr#9d30008
> 1 <- FETCH= 0 at SQLRelay.pm line 379
> 1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
> 'NUM_OF_FIELDS' 7) thr#9d30008
> 1 <- STORE= 1 at SQLRelay.pm line 379
> 1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
> 'driver_FETCHED_ROWS' 0) thr#9d30008
> 1 <- STORE= 1 at SQLRelay.pm line 384
> 1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
> 'driver_param_inout_list') thr#9d30008
> 1 <- FETCH= undef at SQLRelay.pm line 387
> 1 -> rows for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER)
> thr#9d30008
> 2 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
> cache) at SQLRelay.pm line 446
> 1 <- rows= 0 at SQLRelay.pm line 399
> <- execute= '0E0' at sql.pm line 230
> -> fetchrow_arrayref for DBD::SQLRelay::st
> (DBI::st=HASH(0x9d49a84)~0xa2c774c) thr#9d30008
> 1 <- FETCH= 0 ('driver_FETCHED_ROWS' from cache) at SQLRelay.pm line 412
> 1 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
> cache) at SQLRelay.pm line 422
> 1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
> 'driver_FETCHED_ROWS' 1) thr#9d30008
> 1 <- STORE= 1 at SQLRelay.pm line 426
> 1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
> 'ChopBlanks')thr#9d30008
> 1 <- FETCH= '' at SQLRelay.pm line 429
> <- fetchrow_arrayref= [ '7' 'Completed' undef undef '29752604'
> '28168039' '08-10-2006 11:13:08' ] row1 at sql.pm line 255
>
> I have several other requests with similar errors.
>
> --
> Stephen Carville <st...@to...>
> Unix and Network Admin
> Nationwide Totalflood
> 6033 W. Century Blvd
> Los Angeles, CA 90045
> 310-342-3602
>
>
>
|
|
From: Stephen C. <st...@to...> - 2006-08-13 15:58:21
|
I found that if I undef the script handle after each execution, things
seem to work OK. If you use bind variables, Oracle will cache the
compiled script so the impact of a prepare() before each execute is small.
-------- Original Message --------
Subject: Show Stopper?
Date: Thu, 19 Aug 2006 13:39:22 -0700
From: Stephen Carville <st...@to...>
To: SQlRelay List <sql...@li...>
I've been using sqlrelay 0.37 with oracle8 connector, Perl 5.8.x and
Oracle 10g for about two weeks now and I've noticed an ocassional case
where the data returned did not seem right. This was intermittent and
rare -- maybe one or two every thousand order -- but finally a
test case proved to me sqlrelay doesn't always return the correct data.
I sent the follwing SQL:
select a.statid, b.webstatdesc, a.pendid, c.penddesc,
a.certno, a.reqid, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
where a.statid = b.statid
and a.pendid = c.pendid (+)
and tranid = 1
and certno = 29693421
I got back
'7' 'Completed' undef undef '29752604' '28168039' '08-10-2006 11:13:08'
The correct values s/b:
'9' 'Pending' '3' 'Waiting for info from Client' '29693421' '28109417'
'08-10-2006 11:13:08'
Notice the difference in the 'certno' and 'reqid' fields. These _never_
change once an order has been submitted. At first I assumed the orders
were being marked completed in error but as the above shows it is the
data returned that is sometimes wrong.
Here is the results from the DBI trace log:
-> prepare for DBD::SQLRelay::db (DBI::db=HASH(0xa2d42f8)~0xa33a29c
'select
a.statid, b.webstatdesc, a.pendid, c.penddesc,
a.certno, a.reqid, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
where a.statid = b.statid
and a.pendid = c.pendid (+)
and tranid = 1
and certno = 29693421') thr#9d30008
1 <- FETCH= ( SQLRelay::Connection=SCALAR(0xa33a410) ) [1 items]
('driver_connection' from cache) at SQLRelay.pm line 138
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
'driver_database_handle' DBI::db=HASH(0xa33a29c)) thr#9d30008
<- STORE= 1 at SQLRelay.pm line 145
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
'NUM_OF_PARAMS' 0) thr#9d30008
<- STORE= 1 at SQLRelay.pm line 146
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
'driver_is_select' 1) thr#9d30008
<- STORE= 1 at SQLRelay.pm line 147
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
'driver_cursor' SQLRelay::Cursor=SCALAR(0xa2c77dc)) thr#9d30008
<- STORE= 1 at SQLRelay.pm line 148
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
'NUM_OF_PARAMS' 0) thr#9d30008
<- STORE= 1 at SQLRelay.pm line 158
<- prepare= DBI::st=HASH(0x9d49a84) at sql.pm line 223
-> execute for DBD::SQLRelay::st
(DBI::st=HASH(0x9d49a84)~0xa2c774c) thr#9d30008
1 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
cache) at SQLRelay.pm line 349
1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'NUM_OF_FIELDS') thr#9d30008
1 <- FETCH= 0 at SQLRelay.pm line 379
1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'NUM_OF_FIELDS' 7) thr#9d30008
1 <- STORE= 1 at SQLRelay.pm line 379
1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'driver_FETCHED_ROWS' 0) thr#9d30008
1 <- STORE= 1 at SQLRelay.pm line 384
1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'driver_param_inout_list') thr#9d30008
1 <- FETCH= undef at SQLRelay.pm line 387
1 -> rows for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER)
thr#9d30008
2 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
cache) at SQLRelay.pm line 446
1 <- rows= 0 at SQLRelay.pm line 399
<- execute= '0E0' at sql.pm line 230
-> fetchrow_arrayref for DBD::SQLRelay::st
(DBI::st=HASH(0x9d49a84)~0xa2c774c) thr#9d30008
1 <- FETCH= 0 ('driver_FETCHED_ROWS' from cache) at SQLRelay.pm line 412
1 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
cache) at SQLRelay.pm line 422
1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'driver_FETCHED_ROWS' 1) thr#9d30008
1 <- STORE= 1 at SQLRelay.pm line 426
1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'ChopBlanks')thr#9d30008
1 <- FETCH= '' at SQLRelay.pm line 429
<- fetchrow_arrayref= [ '7' 'Completed' undef undef '29752604'
'28168039' '08-10-2006 11:13:08' ] row1 at sql.pm line 255
I have several other requests with similar errors.
--
Stephen Carville <st...@to...>
Unix and Network Admin
Nationwide Totalflood
6033 W. Century Blvd
Los Angeles, CA 90045
310-342-3602
--
Stephen Carville <st...@to...>
Unix and Network Admin
Nationwide Totalflood
6033 W. Century Blvd
Los Angeles, CA 90045
310-342-3602
|
|
From: Stephen C. <st...@to...> - 2006-08-10 23:18:41
|
I've been using sqlrelay 0.37 with oracle8 connector, Perl 5.8.x and
Oracle 10g for about two weeks now and I've noticed an ocassional case
where the data returned did not seem right. This was intermittent and
rare -- maybe one or two every thousand order -- but I finally found a
test case that prove sqlrelay doesn't always return the correct data.
I sent the follwing SQL:
select a.statid, b.webstatdesc, a.pendid, c.penddesc,
a.certno, a.reqid, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
where a.statid = b.statid
and a.pendid = c.pendid (+)
and tranid = 1
and certno = 29693421
I got back
'7' 'Completed' undef undef '29752604' '28168039' '08-10-2006 11:13:08'
The correct values s/b:
'9' 'Pending' '3' 'Waiting for info from Client' '29693421' '28109417'
'08-10-2006 11:13:08'
Notice the difference in the 'certno' and 'reqid' fields. These _never_
change once an order has been submitted. At first I assumed the orders
were being marked completed in error but as the above shows it is the
data returned that is sometimes wrong.
Here is the results from the DBI trace log:
-> prepare for DBD::SQLRelay::db (DBI::db=HASH(0xa2d42f8)~0xa33a29c
'select
a.statid, b.webstatdesc, a.pendid, c.penddesc,
a.certno, a.reqid, to_char(sysdate,'MM-DD-YYYY hh24:mi:ss')
from viewrequestmasall a, requeststatusparm b, pendingreasonparm c
where a.statid = b.statid
and a.pendid = c.pendid (+)
and tranid = 1
and certno = 29693421') thr#9d30008
1 <- FETCH= ( SQLRelay::Connection=SCALAR(0xa33a410) ) [1 items]
('driver_connection' from cache) at SQLRelay.pm line 138
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
'driver_database_handle' DBI::db=HASH(0xa33a29c)) thr#9d30008
<- STORE= 1 at SQLRelay.pm line 145
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
'NUM_OF_PARAMS' 0) thr#9d30008
<- STORE= 1 at SQLRelay.pm line 146
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
'driver_is_select' 1) thr#9d30008
<- STORE= 1 at SQLRelay.pm line 147
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
'driver_cursor' SQLRelay::Cursor=SCALAR(0xa2c77dc)) thr#9d30008
<- STORE= 1 at SQLRelay.pm line 148
-> STORE for DBD::SQLRelay::st (DBI::st=HASH(0x9d49a84)~0xa2c774c
'NUM_OF_PARAMS' 0) thr#9d30008
<- STORE= 1 at SQLRelay.pm line 158
<- prepare= DBI::st=HASH(0x9d49a84) at sql.pm line 223
-> execute for DBD::SQLRelay::st
(DBI::st=HASH(0x9d49a84)~0xa2c774c) thr#9d30008
1 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
cache) at SQLRelay.pm line 349
1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'NUM_OF_FIELDS') thr#9d30008
1 <- FETCH= 0 at SQLRelay.pm line 379
1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'NUM_OF_FIELDS' 7) thr#9d30008
1 <- STORE= 1 at SQLRelay.pm line 379
1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'driver_FETCHED_ROWS' 0) thr#9d30008
1 <- STORE= 1 at SQLRelay.pm line 384
1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'driver_param_inout_list') thr#9d30008
1 <- FETCH= undef at SQLRelay.pm line 387
1 -> rows for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER)
thr#9d30008
2 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
cache) at SQLRelay.pm line 446
1 <- rows= 0 at SQLRelay.pm line 399
<- execute= '0E0' at sql.pm line 230
-> fetchrow_arrayref for DBD::SQLRelay::st
(DBI::st=HASH(0x9d49a84)~0xa2c774c) thr#9d30008
1 <- FETCH= 0 ('driver_FETCHED_ROWS' from cache) at SQLRelay.pm line 412
1 <- FETCH= SQLRelay::Cursor=SCALAR(0xa2c77dc) ('driver_cursor' from
cache) at SQLRelay.pm line 422
1 -> STORE for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'driver_FETCHED_ROWS' 1) thr#9d30008
1 <- STORE= 1 at SQLRelay.pm line 426
1 -> FETCH for DBD::SQLRelay::st (DBI::st=HASH(0xa2c774c)~INNER
'ChopBlanks')thr#9d30008
1 <- FETCH= '' at SQLRelay.pm line 429
<- fetchrow_arrayref= [ '7' 'Completed' undef undef '29752604'
'28168039' '08-10-2006 11:13:08' ] row1 at sql.pm line 255
I have several other request from today with similar errors.
--
Stephen Carville <st...@to...>
Unix and Network Admin
Nationwide Totalflood
6033 W. Century Blvd
Los Angeles, CA 90045
310-342-3602
|
|
From: David M. <dav...@fi...> - 2006-08-05 06:57:35
|
Hello list, I just released sqlrelay-0.37.1. Get it from http://sqlrelay.sourceforge.net/download.html 0.38 is going to have some cool features, but it's just taking too long to get out and there are some updates that I think are critical to release, so I backed them into a 0.37.1 release. Here's the changelog: fixed missing self before __getRow and __getRowRange in python db driver added test for 0 length result set to PySQLRDB's fetchmany method removed erroneous reference to sqlrcon_errormessage in php pear db some oracle unicode clob fixes integrated Andreas Behr's listener crash patch interbase/firebird dead-db/relogin works now The most notable fix is for fetching clobs from oracle containing unicode. While better than 0.36, version 0.37 could potentially truncate or skip segments of the clob. Anyone using oracle unicode clobs should upgrade to 0.37.1, especially if you've noticed any funny behavior. I'll probably follow this release up soon with a 0.37.2 with a few more updates, most notably a large-integer update to the python api. So stay tuned. David Muse dav...@fi... |
|
From: David M. <dav...@fi...> - 2006-08-05 04:36:49
|
Thanks for finding that.
It looks like the code should be replaced with:
// get the address info for the given address/port
addrinfo *ai;
int result;
do {
result=getaddrinfo(_address(),portstr,&hints,&ai);
} while (result==EAI_SYSTEM && error::getErrorNumber()==EINTR);
delete[] portstr;
if (result) {
return RESULT_ERROR;
}
getaddrinfo always returns 0 on success and returns EAI_SYSTEM on a
system error like EINTR.
I'll make sure to fix this in the next release.
Dave
On Wed, 2006-08-02 at 16:43 +0900, seong hoon park wrote:
> In the file src/inetclientsocket.C:145
>
> do {
>
> result=getaddrinfo(_address(),portstr,&hints,&ai);
> } while (result==-1 &&
> error::getErrorNumber()==EINTR);
> delete[] portstr;
> if (result==-1) {
> return RESULT_ERROR;
> }
>
> but return value of getaddraddrinfo() is not only -1 if failed
>
> line 196:
> for (addrinfo *ainfo=ai; ainfo; ainfo=ainfo->ai_next) {
>
> If target hostname doesn't exists ( in my system, getaddrinfo()
> returns -2)
> segmentation fault can occur here as it haven't returned
> with RESULT_ERROR ( I build it with efence library)
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________ Sqlrelay-discussion mailing list Sql...@li... https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion
|
|
From: David M. <dav...@fi...> - 2006-08-05 04:01:29
|
No, a symlink won't work. It's strange that there are no .so files. Maybe there's a mysql-devel rpm that you need to install as well. Dave dav...@fi... On Wed, 2006-08-02 at 10:16 -0700, Ricardo Kleemann wrote: > Hi, > > I have Fedora 5, and the mysql rpms I've installed are the ones for > 5.1 straight from mysql.com > > When I try to compile, I get the errors: > > g++: /usr/lib/mysql/libmysqlclient.so: No such file or directory > g++: /usr/lib/mysql/libz.so: No such file or directory > make[3]: *** [sqlr-connection-mysql] Error 1 > make[3]: Leaving directory > `/root/builds/sqlrelay-0.37/src/connections/mysql' > make[2]: *** [all] Error 2 > make[2]: Leaving directory > `/root/builds/sqlrelay-0.37/src/connections' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/root/builds/sqlrelay-0.37/src' > make: *** [all] Error 2 > > Here's what I have in /usr/lib/mysql: > > [root@db_mgr sqlrelay-0.37]# ls /usr/lib/mysql > libdbug.a libmysqlclient.a libmystrings.a libvio.a > libheap.a libmysqlclient.la libmysys.a libz.a > libmyisam.a libmysqlclient_r.a libndbclient.a libz.la > libmyisammrg.a libmysqlclient_r.la libndbclient.la mysqld-max.sym > > So I have libmysqlclient.a and libz.a but I don't have the .so > versions... would a simple symlink work? > > Ricardo > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ Sqlrelay-discussion mailing list Sql...@li... https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion |