Re: MSSQL and ntext
| From: | Frank M. Kromann | Date: | Thu, 09 Nov 2000 19:07:15 +0000 |
| Subject: | Re: MSSQL and ntext | ||
| Groups: | php.db php.general | ||
| Request: | Send a blank email to php-db+get-4340@lists.php.net to get a copy of this message | ||
Hi,
With MS SQL Server 7.0 you can use NCHAR and NTEXT columns, but these are truncated by the DBLIB
module used with the php extention. If you use CHAR, VARCHAR and TEXT columns you dont have this
problem. For TEXT columns you will have to define mssql.textsize and mssql.textlimit in php.in,
otherwise you will only get 4kb even id the column content is larger than 4kb.
- Frank
>We have an application that is currently
>running in MS Access. It is a bug tracker.
>We have a description and resolution field.
>The max length of data in description
>is 10k long and in resolution is 34k long.
>
>We are porting the application to MSSQL
>and PHP.
>
>In MSSQL my solution for the above columns
>would be to define them as 'ntext' but then
>I found the following problem when I ran
>my PHP script:
>
>"MS SQL message: ntext data cannot be sent
>to clients using DB-Library (such as ISQL)
>or ODBC version 3.7 or earlier."
>
>I am not using ODBC. I am using the provided
>extension (Apache & NT 4).
>
>>From what I can tell there will be a lot
>more coding envolved if I use ntext or text.
>
>Does anybody have any thoughts on this?
>
>Does anybody have another solution for
>storing large amounts of text in MSSQL?
>
>LP
>
>
>__________________________________________________
>Do You Yahoo!?
>Thousands of Stores. Millions of Products. All in one Place.
>http://shopping.yahoo.com/
>
>--
>PHP General Mailing List (http://www.php.net/)
>To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net
>For additional commands, e-mail: php-general-help@lists.php.net
>To contact the list administrators, e-mail: php-list-admin@lists.php.net
>
>
>