FreeTDS Development Group

[Helio Cavichiolo Jr <hcav AT ig.com.br>]

Can you send me the options you use to compile php and apache? Perhaps the 
problem can be there.

The entire script is this:

<?

echo "Conectando...<br>\n";
$connect = odbc_connect("APIS", "sa", "********");
echo "Executando a query...<br>\n";
$query = "select nome from transportador";
$result = odbc_exec($connect, $query);
while (odbc_fetch_row($result)) {
  $nome = odbc_result($result, 1);
  echo "$nome<br>\n";
}
odbc_close($connect);
echo "Fim\n";

?>

This script can be run from these URLs:

http://200.182.158.3/cgi-bin/teste.php
and
http://200.182.158.3/teste.php


Em Seg 14 Out 2002 17:43, you wrote:
> Uhhhhhhmmm, well, "it works for me".
>
> That is, I just installed apache-1.3.27, php-4.1.2, ap-php-4.1.2, and
> php-odbc-4.1.2.  I was able to write a simple select query and execute it,
> get results back, and format them in a table.  This was with an unpatched
> current FreeTDS from CVS.
>
> So, what's different in your environment?  Can you post the rest of your
> php script (remove any passwords of course)?
>
> [I see that freddy77 just committed another fix for odbc...I just updated
> my FreeTDS source, rebuilt, and reinstalled, and made sure it still
> works...with or without his most recent change]
>
> Anyway, I attached the php script that I scraped together based on a couple
> of examples from http://www.php.net/ ... perhaps it will give a clue as to
> what's going wrong in your script?
>
> Cheers,
> --nick
>
> -----Original Message-----
> From: bounce-freetds-145195 AT franklin.oit.unc.edu
> [mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
> Sent: Monday, October 14, 2002 12:59 PM
> To: TDS Development Group
> Subject: [freetds] RE: freetds-0.60 + unixODBC + sqlserver2000 + PHP
>
>
> Nothing changed. I still got the same message:
>
> Warning: SQL error: [unixODBC]Statement option not implemented, SQL state
> 08001 in SQLSetStmtOption in /var/www/htdocs/teste.php on line 7
>
> Lines 6 and 7 are:
>
> $query = "select nome from transportador";
> $result = odbc_exec($connect, $query);
>
> Helio
>
> Em Seg 14 Out 2002 15:10, you wrote:
> > So we probably need the SQLGetInfo() call to return a code indicating
> > that we don't support ExtendedFetch.  Can you try this patch and let
> > me know if it makes any difference?
> >
> > Cheers,
> > --nick
> >
> > -----Original Message-----
> > From: bounce-freetds-145195 AT franklin.oit.unc.edu
> > [mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
> > Sent: Monday, October 14, 2002 12:05 PM
> > To: TDS Development Group
> > Subject: [freetds] RE: freetds-0.60 + unixODBC + sqlserver2000 + PHP
> >
> > Lowden, James K wrote:
> > >>From: Helio Cavichiolo Jr [mailto:hcav AT terra.com.br]
> > >>Sent: October 14, 2002 9:22 AM
> > >>
> > >>As you can see here, in the PHP function call:
> > >>
> > >>#ifdef HAVE_SQL_EXTENDED_FETCH
> > >
> > >          ^^^^^^^^^  This should be undefined, no?
> > >
> > >>/* Solid doesn't have ExtendedFetch, if DriverManager is used, get
> > >>Info,
> > >>    whether Driver supports ExtendedFetch */
> > >>    rc = SQLGetInfo(conn->hdbc, SQL_FETCH_DIRECTION, (void *),
> > >>srollopts, sizeof(scrollopts), NULL);
> > >
> > > FreeTDS's ODBC library doesn't support ExtendedFetch.  Why would
> > > HAVE_SQL_EXTENDED_FETCH be defined?  I would expect this code not to
> > > be compiled (#ifdef tests FALSE).
> >
> > Not if it is compiled against a driver manager. PHP has a lot of stuff
> > like this for direct linking against drivers.
>
> ---
> You are currently subscribed to freetds as: [Nicholas_Castellano AT acml.com]
> To unsubscribe, forward this message to
> $subst('Email.Unsub')
>
>
> The information contained in this transmission may contain privileged and
> confidential information and is intended only for the use of the person(s)
> named above.  If you are not the intended recipient, or an employee or
> agent responsible for delivering this message to the intended recipient,
> any review, dissemination, distribution or duplication of this
> communication is strictly prohibited. If you are not the intended
> recipient, please contact the sender immediately by reply e-mail and
> destroy all copies of the original message. Please note that for certain
> accounts we do not accept orders and/or instructions by e-mail, and for
> those accounts we will not be responsible for carrying out such orders
> and/or instructions. Kindly refrain from sending orders or instructions by
> e-mail unless you have confirmed that we accept such communications for
> your account. Please also note that to satisfy regulatory requirements we
> review the outgoing and incoming e-mail correspondence of staff members
> serving certain functions.