More on the ODBC port...
Since we can't rely on the odbc_num_rows function for counting the result of
select statement, I had to get rid of them all. It took me 1.5 days so far.
Now I have to see where I've broken stuff.
I stumbled across a piece of code that is very strange as well. It's in
order.inc, the part of the code that actually change the order of a question.
I've a feeling that the SQL statement used is not right. But, somehow,
everything seems to work (I didn't investigate completely). So either its
wrong, either is quite clever (I need three SQL operation to get the same
result). So if someone can explain me how this part of the code is working,
it'll be helpful.
stF
> Yes, you read well, ODBC port :)
>
> I'm doing it like that because I have to reduce the risks... Since it's
> gonna work on Oracle, I'll share my experience with you. Right now, I'm
> converting all the mysal_ statements to odbc_ statements. It's not that
> simple. Especially the mysql_num_rows which doesn' translate easily into
> odbc_num_rows (this one is not guaranteed to work on every ODBC driver...).
>
> More on that later.
>
> stF
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by OSDN developer relations
> Here's your chance to show off your extensive product knowledge
> We want to know what you know. Tell us and you have a chance to win $100
> http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
|
