You are my last chance to survive this crisis I am battling now. Not easy to describe the problem, but I will try. I do develop as a member of a project which is an economical software for the internet, using MSSQL6.5 (oh god why:(((), php, perl.
There are two platforms, they were planned to be identical, one is for development, and one for test. They are DEC Alpha systems with Tru64 OS. Until this it is very nice, eh besides MSSQL. MSSQL resides on 2 NT machines. I created some pages with php and perl for users to provide their datas and orders. Everything was beautiful until we copied the whole stuff into the test machine.
It returned some really strange error messages when we requested the same pages. While they worked well on the develop machine, they crashed on the test machine. It said there is no database table which must be there because I checked through MSSQL query at the NT machine and I checked it through some perl scripts I wrote for accessing queries from MSSQL. Finally I realized that every query works well, until I try to send a subquery while an $sth is opened. When no statement handler is present there is no error. When I use a subquery (starting $sth2 for example, it just dies.
So I must call the external perl scripts, because they are running in an other database handler, so there is no conflict. Is not it funny? I am frustrated.
I dont want to paste any code here, because I know that the problem is not in that. The problem must be some incompatibility, so:
develop machine: perl: version 5.004_04 built for alpha-dec_osf, DBI: 1.13
test machine: perl: version 5.005_03 built for alpha-dec_osf, DBI: 1.14
All machines have DBD::Sybase 0.23 and 'freetds' to connect MSSQL. Any help could save my life.
thank you
-- tune
In reply to strange DBI behaviour by tune
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |