Re: PEAR::DB weirdness

On 9/16/05, Jeff Beidler <jeff@greenbirdweb.com> wrote: > > Okay, so I wrote this spiffy little PHP-GTK app. It's my first one, and I'm > proud of it. Works fine by itself, but I wanted to distribute it sans PHP > (the interpreter). I heard about the Roadsend compiler and downloaded their > demo. Looks like it will be fantabulous... if I can get it to work. > > Here's the rub: PCC (the Roadsend compiler) doesn't support the php-mssql > extension (which I need to connect to the company database). So, I look on > PEAR and find DB. Sounds great. I download it, install it, and try it out. > Works fine if I run my app through the PHP interpreter, but not with the > Roadsend compiler. Funny thing is, their support guru says they use > PEAR::DB, even rely on it. Somehow, though (just my luck) it won't work for > me. Whilst tracing the program through the use of the integrated debugger, > it appears to me that the file "common.php" is somehow getting stuck in an > infinite loop, and returning an unknown DB error object. > PEAR::DB is not a replacement for the native DB functions (mysql_* and mssql_*), it's an abstraction layer built on top of them. Hence if you use mssql:// in your DB DSN you're still using the mssql_* functions, just not directly. I would suggest trying ODBC if the compiler supports it. Or switch to mysql. ;-) -- Justin Patrin