RE: RE: [PHP-WIN] SQL Server 7 help needed!!!
| From: | Paco Ortiz | Date: | Thu, 04 Jan 2001 09:52:06 +0000 |
| Subject: | RE: RE: [PHP-WIN] SQL Server 7 help needed!!! | ||
| References: | 1 | Groups: | php.windows |
| Request: | Send a blank email to php-windows+get-4791@lists.php.net to get a copy of this message | ||
Hi:
nice to hear from you, Frank ! (by the way I'm also Frank)
----- Mensaje original -----
De: "Frank M. Kromann" <fmk@swwwing.com>
Para: "Paco Ortiz" <fjortiz@comunet.es>
CC: "php-windows" <php-windows@lists.php.net>
Enviado: Thursday, January 04, 2001 12:41 AM
Asunto: Re: RE: [PHP-WIN] SQL Server 7 help needed!!!
> As you say "dbdatlen" uses the configured max length of text fields. These values can
> be altered from php.ini
>
> mssql.textlimit = 8192 ; valid range 0 - 2147483647 default = 4096
> mssql.textsize = 8192 ; valid range 0 - 2147483647 default = 4096
>
> I have testest this with values up to 256kb and it works fine.
yes, that's what I thought at first, because "dbsetopt" and "SET TEXTSIZE"
is called with those values, but it didn't work for me. Perhaps I did something wrong,
I'll try again now ... glubs I think my php_mssql.dll is not loading properly parameters from
php.ini. I'll check it later to see what's going on. So that was my problem !
> Users of IE browsers are limited to enter up to 64K in a textarea input field >and as you
> point out using large text columns slows down performence so I >would not recomment that.
.. but an increasing number of people uses PHP for intranet projects, where 64k is not such a
problem... that's our case too.
> >So I guess some modifications could be made, perhaps using BLOB-specific functions.
> >Personally I would keep long chunks of text away from a Web app, but handling ir carefully...
>
> Modifications are not needed, as the module can handle large text columns!
good to know...
> >I'm going to ask the maintainer if some work is currentry being done about this.
>
> I'm the maintainer so here is your andwer :-)
If you don't mind, I will ask you a couple of things, now I hear from you:
we have a problem: we use many MSSQL stored procedures. We also need to retrieve return values and
use input/output parameters.
I didn't know whether something was being developed at the time, but I needed it so badly that
I created my own functions:
mssql_init : to initialize an rpc statement
mssql_param: to bind PHP variables to input/output parameters, much like oci_bind does.
mssql_execute: to execute the stored procedure and get a recordset and RETVAL-OUTPUT
parameters.
What do you think about it?. If you want, I can send you my code so far. I have almost finished.
Greetings,
Paco
> - Frank
>
>
>
>
> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: php-windows-unsubscribe@lists.php.net
> For additional commands, e-mail: php-windows-help@lists.php.net
> To contact the list administrators, e-mail: php-list-admin@lists.php.net
>