Dyntex.net Support Centre: MySQL Reference Manual p.555

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

Chapter 8: MySQL APIs 555 Check the MyODBC trace file, to nd out what could be wrong. You should be able to nd out the issued queries by searching after the string >mysql_real_query in the `myodbc.log' le. You should also try duplicating the queries in the mysql monitor or admndemo to nd out if the error is MyODBC or MySQL. If you nd out something is wrong, please only send the relevant rows (max 40 rows) to myodbc@lists.mysql.com. Please never send the whole MyODBC or ODBC log le! If you are unable to nd out what's wrong, the last option is to make an archive (tar or zip) that contains a MyODBC trace le, the ODBC log le, and a README le that explains the problem. You can send this to ftp://support.mysql.com/pub/mysql/secret/. Only we at MySQL AB will have access to the les you upload, and we will be very discrete with the data! If you can create a program that also shows this problem, please upload this too! If the program works with some other SQL server, you should make an ODBC log le where you do exactly the same thing in the other SQL server. Remember that the more information you can supply to us, the more likely it is that we can x the problem! 8.4 MySQL C API The C API code is distributed with MySQL. It is included in the mysqlclient library and allows C programs to access a database. Many of the clients in the MySQL source distribution are written in C. If you are looking for examples that demonstrate how to use the C API, take a look at these clients. You can nd these in the clients directory in the MySQL source distribution. Most of the other client APIs (all except Java) use the mysqlclient library to communicate with the MySQL server. This means that, for example, you can take advantage of many of the same environment variables that are used by other client programs, because they are referenced from the library. See Section 4.8 [Client-Side Scripts], page 287, for a list of these variables. The client has a maximum communication buer size. The size of the buer that is allocated initially (16K bytes) is automatically increased up to the maximum size (the maximum is 16M). Because buer sizes are increased only as demand warrants, simply increasing the default maximum limit does not in itself cause more resources to be used. This size check is mostly a check for erroneous queries and communication packets. The communication buer must be large enough to contain a single SQL statement (for client-to-server trac) and one row of returned data (for server-to-client trac). Each thread's communication buer is dynamically enlarged to handle any query or row up to the maximum limit. For example, if you have BLOB values that contain up to 16M of data, you must have a communication buer limit of at least 16M (in both server and client). The client's default maximum is 16M, but the default maximum in the server is 1M. You can increase this by changing the value of the max_allowed_packet parameter when the server is started. See Section 5.5.2 [Server parameters], page 363.

MySQL Reference Manual

Our Partners

SpiritHost - web hosting for spiritual and education sites
SpiritHit.com - Religious and Spiritual Portal

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide