summaryrefslogtreecommitdiff
path: root/include/mysql_com.h
Commit message (Collapse)AuthorAgeFilesLines
* Add support for up to VARCHAR (size up to 65535)monty@mysql.com2004-12-061-1/+1
| | | | | | | | | Renamed HA_VAR_LENGTH to HA_VAR_LENGTH_PART Renamed in all files FIELD_TYPE_STRING and FIELD_TYPE_VAR_STRING to MYSQL_TYPE_STRING and MYSQL_TYPE_VAR_STRING to make it easy to catch all possible errors Added support for VARCHAR KEYS to heap Removed support for ISAM Now only long VARCHAR columns are changed to TEXT on demand (not CHAR) Internal temporary files can now use fixed length tables if the used VARCHAR columns are short
* Merge with 4.1 to get in latest bug fixesmonty@mysql.com2004-11-041-6/+0
|\
| * Remove usage of !$ from mysql-testsmonty@mysql.com2004-11-021-6/+0
| | | | | | | | | | | | Added protocol::flush() for easier embedded-server code Increase block allocation variables a bit as they where a bit too small for MySQL 4.1 Added option --silent to client_test
* | merge with 4.1monty@mysql.com2004-10-291-2/+10
|\ \ | |/
| * added missing command names to command_name[] arrayserg@serg.mylan2004-10-221-2/+5
| |
| * BUG#4788 - show create table provides incorrect statement.ingo@mysql.com2004-09-101-0/+5
| | | | | | | | | | | | Added code to adjust the field_length of user variables in dependence on the field type. Aded new constants for numeric field widths.
* | Strict mode & better warningsmonty@mishka.local2004-09-281-0/+1
| | | | | | | | | | | | Under strict mode MySQL will generate an error message if there was any conversion when assigning data to a field. Added checking of date/datetime fields. If strict mode, give error if we have not given value to field without a default value (for INSERT)
* | Merge with 4.1monty@mysql.com2004-09-061-17/+24
|\ \ | |/ | | | | | | (Includes merge of arena code in 4.1 and 5.0)
| * Fixed symbol name problems that made build fail.pem@mysql.comhem.se2004-08-191-6/+6
| |
| * mysql_com.h:guilhem@mysql.com2004-08-191-11/+7
| | | | | | | | still better names for enum; removing unneeded symbol
| * mysql_com.h:guilhem@mysql.com2004-08-191-9/+9
| | | | | | | | Better names for defines, as these are visible in API
| * Very small API change: changing the values in enum enum_shutdown_level;guilhem@mysql.com2004-08-191-16/+27
| | | | | | | | | | | | | | as this enum is not really usable yet (as MySQL server supports only one shutdown level), and as SHUTDOWN_DEFAULT is still left to 0, this change should disturb no user. Later (in 4.1.4 or 4.1.5) code will be pushed to implement graceful shutdown using this enum.
* | Port of cursors to be pushed into 5.0 tree:konstantin@mysql.com2004-08-031-1/+22
| | | | | | | | | | | | | | - client side part is simple and may be considered stable - server side part now just joggles with THD state to save execution state and has no additional locking wisdom. Lot's of it are to be rewritten.
* | enum_server_commandkonstantin@mysql.com2004-07-281-0/+5
| |
* | Merge with 4.1.3-betamonty@mysql.com2004-07-071-9/+26
|\ \ | |/
| * Including in enum_shutdown_level the 2 types of KILL of 5.0guilhem@mysql.com2004-06-211-1/+5
| | | | | | | | (enum_shutdown_level is going to replace enum killed_state in 5.0).
| * changing order of enum_shutdown_level (easier; we can test if we should die withguilhem@mysql.com2004-06-211-5/+6
| | | | | | | | | | "if (thd->killed > thd->killable)", if we simply do thd->killed= level;
| * API change: mysql_shutdown() now requires a 2nd argument, the shutdown level.guilhem@mysql.com2004-06-181-2/+2
| | | | | | | | | | | | | | | | mysqld >=4.1.3 will however understand shutdown requests sent by clients <4.1.3. And mysqld <4.1.3 will understand shutdown requests sent by clients >=4.1.3 (it will ignore the level). Those shutdown level are just PLACEHOLDERS now. So this change is just to make the 4.1 API suitable before it is frozen. Later we will actually implement the shutdown levels.
| * Adding SHUTDOWN_WAIT_STATEMENTS to the possible arguments of mysql_shutdown().guilhem@mysql.com2004-06-151-2/+3
| | | | | | | | Comments on names still welcome.
| * API change: mysql_shutdown() now needs a 2nd parameter, the shutdown level.guilhem@mysql.com2004-06-151-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | Server will however still accept shutdown without specified level; so that old mysqladmin can still shut server down. I would like your comments on the names of shutdown level which I chose. You are welcome to propose better names. Please however check WL#709 before. Reason for the names I propose is to be accurate, thus leaving possibility for other levels which we may imagine in the future; that's why I have rejected names like "fast", "smart", "graceful" so far. My position is that WAIT_ALL_BUFFERS or WAIT_CRITICAL_BUFFERS say what the shutdown does, whereas for "smart", "fast" you need to remember what it does. This should be pushed in 4.1.3 but only after your comments.
| * merge with 4.0 to get windows fixesmonty@mysql.com2004-05-271-9/+0
| |\
| | * Fix to make Windows compilation smootherhf@deer.(none)2004-05-261-9/+0
| | |
* | | Merging 4.1 to 5.0.pem@mysql.com2004-05-261-3/+9
|\ \ \ | |/ /
| * | merge with 4.0 to get Netware patches and fixes for libmysqld.dllmonty@mysql.com2004-05-251-2/+8
| |\ \ | | |/
| | * Proposed fix for bug #3818 (libmysqld.dll leads to program's crash)hf@deer.(none)2004-05-261-2/+8
| | | | | | | | | | | | | | | configurations added to build the libraries with USE_TLS flag to be used for libmysqld
| * | Support for character set conversion in binary protocol: another gokonstantin@mysql.com2004-05-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | after Monty's review. - Item_param was rewritten. - it turns out that we can't convert string data to character set of connection on the fly, because they first should be written to the binary log. To support efficient conversion we need to rewrite prepared statements binlogging code first.
* | | Merge 4.1 -> 5.0pem@mysql.com2004-05-071-11/+0
|\ \ \ | |/ /
| * | Fix for Bug#3035 "Prepared statement integer inserts": now unsignedkonstantin@mysql.com2004-04-301-11/+0
| | | | | | | | | | | | | | | | | | | | | flag is sent to server with placeholder types. There were no need to extend the protocol as one additional byte was reserved for placeholder code, when placeholder code is in range 0-255. So this byte is now used for flags. Post-review fixes added.
* | | Merge 4.1 -> 5.0.pem@mysql.com2004-04-071-1/+2
|\ \ \ | |/ /
| * | Fixed many compiler warningsmonty@mysql.com2004-04-051-1/+1
| | | | | | | | | | | | | | | | | | Fixed bugs in group_concat with ORDER BY and DISTINCT (Bugs #2695, #3381 and #3319) Fixed crash when doing rollback in slave and the io thread catched up with the sql thread Set locked_in_memory properly
| * | 1. New data types, from the user point of view:bar@bar.intranet.mysql.r18.ru2004-03-261-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BINARY(N) and VARBIBARY(N) 2. More 4.0 compatibility and more BINARY keyword consistency: 2a. CREATE TABLE a (a CHAR(N) BINARY) is now synonym for CREATE TABLE a (a CHAR(N) COLLATE xxxx_bin) 2b. SELECT BINARY x is still synonin for SELECT x COLLATE xxxxx_bin.
* | | Merge 4.1 to 5.0.pem@mysql.com2003-12-191-1/+1
|\ \ \ | |/ /
| * | Merge with 4.0.17monty@mysql.com2003-12-171-1/+1
| |\ \ | | |/
| | * Fixed a possible memory leak on MacOSX when using the shared libmysql.so ↵monty@mysql.com2003-12-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | library (Bug #2061) mysql_server_init() now returns error code if something went wrong (Bug #2062) Don't use my_fopen() when reading symlink information as this may cause problems when a lot of files are opened. Free thread keys with pthread_key_delete() instead of relying on automatic free. (Bug #2062) Fixed bug in UNION statement with alias '*'. (Bug #1249) Fixed a bug in DELETE ... ORDER BY ... LIMIT where the rows where not deleted in the proper order. (Bug #1024). FOUND_ROWS() could return incorrect number of rows after a query with an impossible WHERE condition. HOW DATABASES doesn't anymore show .sym files (on windows) that doesn't point to a valid directory. (Bug #1385)
* | | Merged 4.1 -> 5.0pem@mysql.com2003-12-091-0/+2
|\ \ \ | |/ /
| * | QUERY_NO_GOOD_INDEX_USED and QUERY_NO_INDEX_USED moved from ↵serg@serg.mylan2003-12-061-0/+2
| | | | | | | | | | | | thd->lex.select_lex->options to thd->server_status
* | | Merge 4.1 to 5.0pem@mysql.com2003-12-011-1/+1
|\ \ \ | |/ /
| * | Fixed compiler warnings from Intel compiler in Win64monty@mysql.com2003-11-231-1/+1
| | | | | | | | | | | | | | | | | | Added option --max-record-length=# to myisamchk Don't try repair twice if doing myisamchk --repair --force Shared memory handler didn't clean up things on errors or shutdown
* | | Fixed BUG#1965: Opening a cursor hangs client when malformed select failspem@mysql.comhem.se2003-11-271-1/+2
| | | | | | | | | | | | and BUG#1966: "select 1 into a" on top-level hangs client
* | | Merging 4.1->5.0.pem@mysql.com2003-11-191-0/+4
|\ \ \ | |/ / |/| |
| * | Merging 4.1->5.0pem@mysql.com2003-10-221-0/+4
| |\ \
| | * \ Merge laptop.sanja.is.com.ua:/home/bell/mysql/bk/mysql-5.0bell@laptop.sanja.is.com.ua2003-09-281-0/+2
| | |\ \ | | | | | | | | | | | | | | | into laptop.sanja.is.com.ua:/home/bell/mysql/bk/work-udf-5.0
| | | * | new UDF arguments interface (WL#1017) (SCRUM)bell@sanja.is.com.ua2003-09-131-0/+2
| | | | |
| | * | | Merging 4.1 -> 5.0pem@mysql.com2003-09-241-0/+2
| | |\ \ \ | | | |/ /
| | | * | Merge 4.1 into 5.0pem@mysql.com2003-08-261-0/+2
| | | |\ \
| | | | * \ Merge 4.1 into 5.0 (first pass).pem@mysql.telia.com2003-07-081-0/+2
| | | | |\ \
| | | | | * \ Merged 4.1 to 5.0.pem@mysql.com2003-04-291-0/+2
| | | | | |\ \
| | | | | | * \ Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-5.0hf@genie.(none)2003-03-311-0/+2
| | | | | | |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | into genie.(none):/home/hf/work/mysql-5.0.kil
| | | | | | | * | SCRUMhf@genie.(none)2003-03-211-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | two versions of KILL implementation
* | | | | | | | | CLIENT_MULTI_QUERIES -> CLIENT_MULTI_STATEMENTSmonty@mashka.mysql.fi2003-11-181-2/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New multi-key-cache handling. This was needed becasue the old one didn't work reliable with MERGE tables. ALTER TABLE table_name ... CHARACTER SET ... now changes all char/varchar/text columns to the given character set (One must use ALTER TABLE ... DEFAULT CHARACTER SET ... to change the default character set) Fixed that have_compress is detected properly (fixes problems with func_compress.test on platforms without zlib) New syntax for CACHE INDEX ('keys' is optional if no index name is given and one mentions the key cache name only ones) Removed compiler warnings Added mysql_set_server_option() to allow clients like PHP to easaily set/reset the multi-statement flag.
View Lorry Controller Status