|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|
||||||||
|
|||||||||
|
|
|
|
Company
|
|
 SQL LINKS DEVELOPER SUPPORT
SEARCH Borland Online/Developer Support
Subject: SQL Anywhere problems + solutions (11/6/96) BDE 3.5 takes care of any known issues with the ODBC driver that came with SQL Anywhere ver 5.0. The ODBC driver I have for this version is marked as ver 4.00.00, dated 1/15/95; there are some patches. Here is the rub, there is now SQL Anywhere ver. 5.5 with a new ODBC driver that BDE 3.5 will fail reading indexes from; ODBC version 5.00.00 9/23/96. This is a known Sybase/Powersoft problem. Refer customers to Powersoft and the tracking number 372138; a patch is forthcoming. According to Powersoft, the current workaround is to use the old ODBC driver (4.00.00). SQL Anywhere 5.5 does not have any new features that would be lost using the old ODBC driver. >>>>>>>>>>>>>>>>>>>>>>>> Date: 10/29/96 1:52pm Subject: SQL Anywhere All, Sybase has found the problem in the SQL Anywhere 5.5 ODBC driver and should have a fix within two weeks. Sybase will send us the ODBC patch as soon as it is available. Answers to other questions, 1)Max index name length is 128 Characters 2)Max # of indexes 32K per table and 32K per column 3)The old ODBC driver will work with the new server (5.5)* *Two versions of 5.5 exist. Standard 5.5 is 5.0 with all the maintenance releases rolled into it. 5.5 Professional is the same plus it includes Internet tools/connectivity. >>>>>>>>>>>>>>>>>>>>> SQLStatistics() now returns the data type for TABLE_NAME, INDEX_NAME correctly as SQL_VARCHAR ( earlier in 5.0 use to return as SQL_LONGVARCHAR) but the column precision returned is 128 for TABLE_NAME and 32676 for INDEX_NAME. The INDEX_NAME precision should also be 128 (SQL_MAX_TABLE_NAME_SIZE) and that's the problem and reason for the following failures in SQL Anywhere 5.3 and above 1. Cannot open a table. 2. Index information is Junk. 3. Blobs don't work. I noted the following SQL Anywhere specific behaviour and i am not sure whether they are as per their design. a. You can create any number of unique index on a single column provided the index name is different. b. There no restriction on the no. of characters we specify for the INDEX NAME. Sybase fixed data type information but broke the precision information, which was returned correctly in SQL AnyWhere 5.0. PUB ODBC BDE ERROR CJ
|
|
||
|
|
|
|||
|
|||||
|
|
||||
 |
|||||
|
|||||
| Made in Borland® Copyright© 1994-2003 Borland Software Corporation. All rights reserved. Report Piracy, Legal Notices, Privacy Policy Last Modified Monday, 26-Mar-2001 16:27:08 PST |
|||||
