2009-09-23 23:32:31 +02:00
|
|
|
#ifndef STRUCTS_INCLUDED
|
|
|
|
#define STRUCTS_INCLUDED
|
|
|
|
|
2006-12-31 01:02:27 +01:00
|
|
|
/* Copyright (C) 2000-2006 MySQL AB
|
2001-12-06 13:10:51 +01:00
|
|
|
|
2000-07-31 21:29:14 +02:00
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
|
|
it under the terms of the GNU General Public License as published by
|
2006-12-23 20:17:15 +01:00
|
|
|
the Free Software Foundation; version 2 of the License.
|
2001-12-06 13:10:51 +01:00
|
|
|
|
2000-07-31 21:29:14 +02:00
|
|
|
This program is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
GNU General Public License for more details.
|
2001-12-06 13:10:51 +01:00
|
|
|
|
2000-07-31 21:29:14 +02:00
|
|
|
You should have received a copy of the GNU General Public License
|
|
|
|
along with this program; if not, write to the Free Software
|
|
|
|
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA */
|
|
|
|
|
|
|
|
|
|
|
|
/* The old structures from unireg */
|
|
|
|
|
|
|
|
struct st_table;
|
|
|
|
class Field;
|
|
|
|
|
2003-11-03 13:01:59 +01:00
|
|
|
typedef struct st_date_time_format {
|
|
|
|
uchar positions[8];
|
|
|
|
char time_separator; /* Separator between hour and minute */
|
|
|
|
uint flag; /* For future */
|
|
|
|
LEX_STRING format;
|
|
|
|
} DATE_TIME_FORMAT;
|
2000-07-31 21:29:14 +02:00
|
|
|
|
|
|
|
|
|
|
|
typedef struct st_keyfile_info { /* used with ha_info() */
|
WL#3817: Simplify string / memory area types and make things more consistent (first part)
The following type conversions was done:
- Changed byte to uchar
- Changed gptr to uchar*
- Change my_string to char *
- Change my_size_t to size_t
- Change size_s to size_t
Removed declaration of byte, gptr, my_string, my_size_t and size_s.
Following function parameter changes was done:
- All string functions in mysys/strings was changed to use size_t
instead of uint for string lengths.
- All read()/write() functions changed to use size_t (including vio).
- All protocoll functions changed to use size_t instead of uint
- Functions that used a pointer to a string length was changed to use size_t*
- Changed malloc(), free() and related functions from using gptr to use void *
as this requires fewer casts in the code and is more in line with how the
standard functions work.
- Added extra length argument to dirname_part() to return the length of the
created string.
- Changed (at least) following functions to take uchar* as argument:
- db_dump()
- my_net_write()
- net_write_command()
- net_store_data()
- DBUG_DUMP()
- decimal2bin() & bin2decimal()
- Changed my_compress() and my_uncompress() to use size_t. Changed one
argument to my_uncompress() from a pointer to a value as we only return
one value (makes function easier to use).
- Changed type of 'pack_data' argument to packfrm() to avoid casts.
- Changed in readfrm() and writefrom(), ha_discover and handler::discover()
the type for argument 'frmdata' to uchar** to avoid casts.
- Changed most Field functions to use uchar* instead of char* (reduced a lot of
casts).
- Changed field->val_xxx(xxx, new_ptr) to take const pointers.
Other changes:
- Removed a lot of not needed casts
- Added a few new cast required by other changes
- Added some cast to my_multi_malloc() arguments for safety (as string lengths
needs to be uint, not size_t).
- Fixed all calls to hash-get-key functions to use size_t*. (Needed to be done
explicitely as this conflict was often hided by casting the function to
hash_get_key).
- Changed some buffers to memory regions to uchar* to avoid casts.
- Changed some string lengths from uint to size_t.
- Changed field->ptr to be uchar* instead of char*. This allowed us to
get rid of a lot of casts.
- Some changes from true -> TRUE, false -> FALSE, unsigned char -> uchar
- Include zlib.h in some files as we needed declaration of crc32()
- Changed MY_FILE_ERROR to be (size_t) -1.
- Changed many variables to hold the result of my_read() / my_write() to be
size_t. This was needed to properly detect errors (which are
returned as (size_t) -1).
- Removed some very old VMS code
- Changed packfrm()/unpackfrm() to not be depending on uint size
(portability fix)
- Removed windows specific code to restore cursor position as this
causes slowdown on windows and we should not mix read() and pread()
calls anyway as this is not thread safe. Updated function comment to
reflect this. Changed function that depended on original behavior of
my_pwrite() to itself restore the cursor position (one such case).
- Added some missing checking of return value of malloc().
- Changed definition of MOD_PAD_CHAR_TO_FULL_LENGTH to avoid 'long' overflow.
- Changed type of table_def::m_size from my_size_t to ulong to reflect that
m_size is the number of elements in the array, not a string/memory
length.
- Moved THD::max_row_length() to table.cc (as it's not depending on THD).
Inlined max_row_length_blob() into this function.
- More function comments
- Fixed some compiler warnings when compiled without partitions.
- Removed setting of LEX_STRING() arguments in declaration (portability fix).
- Some trivial indentation/variable name changes.
- Some trivial code simplifications:
- Replaced some calls to alloc_root + memcpy to use
strmake_root()/strdup_root().
- Changed some calls from memdup() to strmake() (Safety fix)
- Simpler loops in client-simple.c
2007-05-10 11:59:39 +02:00
|
|
|
uchar ref[MAX_REFLENGTH]; /* Pointer to current row */
|
|
|
|
uchar dupp_ref[MAX_REFLENGTH]; /* Pointer to dupp row */
|
2000-07-31 21:29:14 +02:00
|
|
|
uint ref_length; /* Length of ref (1-8) */
|
|
|
|
uint block_size; /* index block size */
|
|
|
|
File filenr; /* (uniq) filenr for table */
|
|
|
|
ha_rows records; /* Records i datafilen */
|
|
|
|
ha_rows deleted; /* Deleted records */
|
|
|
|
ulonglong data_file_length; /* Length off data file */
|
|
|
|
ulonglong max_data_file_length; /* Length off data file */
|
|
|
|
ulonglong index_file_length;
|
|
|
|
ulonglong max_index_file_length;
|
|
|
|
ulonglong delete_length; /* Free bytes */
|
|
|
|
ulonglong auto_increment_value;
|
|
|
|
int errkey,sortkey; /* Last errorkey and sorted by */
|
|
|
|
time_t create_time; /* When table was created */
|
|
|
|
time_t check_time;
|
|
|
|
time_t update_time;
|
|
|
|
ulong mean_rec_length; /* physical reclength */
|
|
|
|
} KEYFILE_INFO;
|
|
|
|
|
|
|
|
|
|
|
|
typedef struct st_key_part_info { /* Info about a key part */
|
|
|
|
Field *field;
|
|
|
|
uint offset; /* offset in record (from 0) */
|
2002-07-17 14:17:20 +02:00
|
|
|
uint null_offset; /* Offset to null_bit in record */
|
2006-06-14 19:06:02 +02:00
|
|
|
uint16 length; /* Length of keypart value in bytes */
|
|
|
|
/*
|
|
|
|
Number of bytes required to store the keypart value. This may be
|
|
|
|
different from the "length" field as it also counts
|
|
|
|
- possible NULL-flag byte (see HA_KEY_NULL_LENGTH)
|
|
|
|
- possible HA_KEY_BLOB_LENGTH bytes needed to store actual value length.
|
|
|
|
*/
|
2000-07-31 21:29:14 +02:00
|
|
|
uint16 store_length;
|
|
|
|
uint16 key_type;
|
|
|
|
uint16 fieldnr; /* Fieldnum in UNIREG */
|
2004-12-19 19:25:19 +01:00
|
|
|
uint16 key_part_flag; /* 0 or HA_REVERSE_SORT */
|
2000-07-31 21:29:14 +02:00
|
|
|
uint8 type;
|
2002-07-17 14:17:20 +02:00
|
|
|
uint8 null_bit; /* Position to null_bit */
|
2000-07-31 21:29:14 +02:00
|
|
|
} KEY_PART_INFO ;
|
|
|
|
|
|
|
|
|
|
|
|
typedef struct st_key {
|
|
|
|
uint key_length; /* Tot length of key */
|
2007-10-26 12:37:38 +02:00
|
|
|
ulong flags; /* dupp key and pack flags */
|
2000-07-31 21:29:14 +02:00
|
|
|
uint key_parts; /* How many key_parts */
|
|
|
|
uint extra_length;
|
|
|
|
uint usable_key_parts; /* Should normally be = key_parts */
|
2006-05-03 14:59:17 +02:00
|
|
|
uint block_size;
|
2002-04-12 20:35:46 +02:00
|
|
|
enum ha_key_alg algorithm;
|
2005-11-05 12:20:35 +01:00
|
|
|
/*
|
|
|
|
Note that parser is used when the table is opened for use, and
|
|
|
|
parser_name is used when the table is being created.
|
|
|
|
*/
|
|
|
|
union
|
|
|
|
{
|
2007-04-02 20:38:58 +02:00
|
|
|
plugin_ref parser; /* Fulltext [pre]parser */
|
2005-11-05 12:20:35 +01:00
|
|
|
LEX_STRING *parser_name; /* Fulltext [pre]parser name */
|
|
|
|
};
|
2000-07-31 21:29:14 +02:00
|
|
|
KEY_PART_INFO *key_part;
|
|
|
|
char *name; /* Name of key */
|
2004-09-08 00:07:53 +02:00
|
|
|
/*
|
|
|
|
Array of AVG(#records with the same field value) for 1st ... Nth key part.
|
|
|
|
0 means 'not known'.
|
|
|
|
For temporary heap tables this member is NULL.
|
|
|
|
*/
|
|
|
|
ulong *rec_per_key;
|
2000-08-15 19:09:37 +02:00
|
|
|
union {
|
2000-08-17 00:05:02 +02:00
|
|
|
int bdb_return_if_eq;
|
2000-08-15 19:09:37 +02:00
|
|
|
} handler;
|
2004-12-06 01:00:37 +01:00
|
|
|
struct st_table *table;
|
2000-07-31 21:29:14 +02:00
|
|
|
} KEY;
|
|
|
|
|
|
|
|
|
|
|
|
struct st_join_table;
|
|
|
|
|
|
|
|
typedef struct st_reginfo { /* Extra info about reg */
|
|
|
|
struct st_join_table *join_tab; /* Used by SELECT() */
|
|
|
|
enum thr_lock_type lock_type; /* How database is used */
|
|
|
|
bool not_exists_optimize;
|
2009-06-26 21:57:42 +02:00
|
|
|
/*
|
|
|
|
TRUE <=> range optimizer found that there is no rows satisfying
|
|
|
|
table conditions.
|
|
|
|
*/
|
2000-07-31 21:29:14 +02:00
|
|
|
bool impossible_range;
|
|
|
|
} REGINFO;
|
|
|
|
|
|
|
|
|
|
|
|
struct st_read_record; /* For referense later */
|
|
|
|
class SQL_SELECT;
|
|
|
|
class THD;
|
|
|
|
class handler;
|
|
|
|
|
|
|
|
typedef struct st_read_record { /* Parameter to read_record */
|
|
|
|
struct st_table *table; /* Head-form */
|
|
|
|
handler *file;
|
|
|
|
struct st_table **forms; /* head and ref forms */
|
|
|
|
int (*read_record)(struct st_read_record *);
|
|
|
|
THD *thd;
|
|
|
|
SQL_SELECT *select;
|
|
|
|
uint cache_records;
|
|
|
|
uint ref_length,struct_length,reclength,rec_cache_size,error_offset;
|
|
|
|
uint index;
|
WL#3817: Simplify string / memory area types and make things more consistent (first part)
The following type conversions was done:
- Changed byte to uchar
- Changed gptr to uchar*
- Change my_string to char *
- Change my_size_t to size_t
- Change size_s to size_t
Removed declaration of byte, gptr, my_string, my_size_t and size_s.
Following function parameter changes was done:
- All string functions in mysys/strings was changed to use size_t
instead of uint for string lengths.
- All read()/write() functions changed to use size_t (including vio).
- All protocoll functions changed to use size_t instead of uint
- Functions that used a pointer to a string length was changed to use size_t*
- Changed malloc(), free() and related functions from using gptr to use void *
as this requires fewer casts in the code and is more in line with how the
standard functions work.
- Added extra length argument to dirname_part() to return the length of the
created string.
- Changed (at least) following functions to take uchar* as argument:
- db_dump()
- my_net_write()
- net_write_command()
- net_store_data()
- DBUG_DUMP()
- decimal2bin() & bin2decimal()
- Changed my_compress() and my_uncompress() to use size_t. Changed one
argument to my_uncompress() from a pointer to a value as we only return
one value (makes function easier to use).
- Changed type of 'pack_data' argument to packfrm() to avoid casts.
- Changed in readfrm() and writefrom(), ha_discover and handler::discover()
the type for argument 'frmdata' to uchar** to avoid casts.
- Changed most Field functions to use uchar* instead of char* (reduced a lot of
casts).
- Changed field->val_xxx(xxx, new_ptr) to take const pointers.
Other changes:
- Removed a lot of not needed casts
- Added a few new cast required by other changes
- Added some cast to my_multi_malloc() arguments for safety (as string lengths
needs to be uint, not size_t).
- Fixed all calls to hash-get-key functions to use size_t*. (Needed to be done
explicitely as this conflict was often hided by casting the function to
hash_get_key).
- Changed some buffers to memory regions to uchar* to avoid casts.
- Changed some string lengths from uint to size_t.
- Changed field->ptr to be uchar* instead of char*. This allowed us to
get rid of a lot of casts.
- Some changes from true -> TRUE, false -> FALSE, unsigned char -> uchar
- Include zlib.h in some files as we needed declaration of crc32()
- Changed MY_FILE_ERROR to be (size_t) -1.
- Changed many variables to hold the result of my_read() / my_write() to be
size_t. This was needed to properly detect errors (which are
returned as (size_t) -1).
- Removed some very old VMS code
- Changed packfrm()/unpackfrm() to not be depending on uint size
(portability fix)
- Removed windows specific code to restore cursor position as this
causes slowdown on windows and we should not mix read() and pread()
calls anyway as this is not thread safe. Updated function comment to
reflect this. Changed function that depended on original behavior of
my_pwrite() to itself restore the cursor position (one such case).
- Added some missing checking of return value of malloc().
- Changed definition of MOD_PAD_CHAR_TO_FULL_LENGTH to avoid 'long' overflow.
- Changed type of table_def::m_size from my_size_t to ulong to reflect that
m_size is the number of elements in the array, not a string/memory
length.
- Moved THD::max_row_length() to table.cc (as it's not depending on THD).
Inlined max_row_length_blob() into this function.
- More function comments
- Fixed some compiler warnings when compiled without partitions.
- Removed setting of LEX_STRING() arguments in declaration (portability fix).
- Some trivial indentation/variable name changes.
- Some trivial code simplifications:
- Replaced some calls to alloc_root + memcpy to use
strmake_root()/strdup_root().
- Changed some calls from memdup() to strmake() (Safety fix)
- Simpler loops in client-simple.c
2007-05-10 11:59:39 +02:00
|
|
|
uchar *ref_pos; /* pointer to form->refpos */
|
|
|
|
uchar *record;
|
|
|
|
uchar *rec_buf; /* to read field values after filesort */
|
|
|
|
uchar *cache,*cache_pos,*cache_end,*read_positions;
|
2000-07-31 21:29:14 +02:00
|
|
|
IO_CACHE *io_cache;
|
2003-02-17 01:14:37 +01:00
|
|
|
bool print_error, ignore_not_found_rows;
|
2000-07-31 21:29:14 +02:00
|
|
|
} READ_RECORD;
|
|
|
|
|
2003-11-03 13:01:59 +01:00
|
|
|
|
2004-06-24 17:08:36 +02:00
|
|
|
/*
|
2007-03-23 21:08:31 +01:00
|
|
|
Originally MySQL used MYSQL_TIME structure inside server only, but since
|
2004-06-24 17:08:36 +02:00
|
|
|
4.1 it's exported to user in the new client API. Define aliases for
|
|
|
|
new names to keep existing code simple.
|
|
|
|
*/
|
|
|
|
|
|
|
|
typedef enum enum_mysql_timestamp_type timestamp_type;
|
2000-07-31 21:29:14 +02:00
|
|
|
|
2003-11-03 13:01:59 +01:00
|
|
|
|
2000-07-31 21:29:14 +02:00
|
|
|
typedef struct {
|
2004-04-28 16:45:08 +02:00
|
|
|
ulong year,month,day,hour;
|
|
|
|
ulonglong minute,second,second_part;
|
2000-07-31 21:29:14 +02:00
|
|
|
bool neg;
|
|
|
|
} INTERVAL;
|
|
|
|
|
|
|
|
|
2003-11-03 13:01:59 +01:00
|
|
|
typedef struct st_known_date_time_format {
|
|
|
|
const char *format_name;
|
|
|
|
const char *date_format;
|
|
|
|
const char *datetime_format;
|
|
|
|
const char *time_format;
|
|
|
|
} KNOWN_DATE_TIME_FORMAT;
|
|
|
|
|
2000-12-26 16:34:04 +01:00
|
|
|
enum SHOW_COMP_OPTION { SHOW_OPTION_YES, SHOW_OPTION_NO, SHOW_OPTION_DISABLED};
|
2002-10-02 12:33:08 +02:00
|
|
|
|
|
|
|
extern const char *show_comp_option_name[];
|
|
|
|
|
2006-01-07 14:41:57 +01:00
|
|
|
typedef int *(*update_var)(THD *, struct st_mysql_show_var *);
|
2002-06-12 23:13:12 +02:00
|
|
|
|
2000-07-31 21:29:14 +02:00
|
|
|
typedef struct st_lex_user {
|
|
|
|
LEX_STRING user, host, password;
|
|
|
|
} LEX_USER;
|
|
|
|
|
2004-12-29 18:30:37 +01:00
|
|
|
/*
|
|
|
|
This structure specifies the maximum amount of resources which
|
|
|
|
can be consumed by each account. Zero value of a member means
|
|
|
|
there is no limit.
|
|
|
|
*/
|
2002-05-15 12:50:38 +02:00
|
|
|
typedef struct user_resources {
|
2004-12-29 18:30:37 +01:00
|
|
|
/* Maximum number of queries/statements per hour. */
|
|
|
|
uint questions;
|
|
|
|
/*
|
|
|
|
Maximum number of updating statements per hour (which statements are
|
2006-06-20 12:20:32 +02:00
|
|
|
updating is defined by sql_command_flags array).
|
2004-12-29 18:30:37 +01:00
|
|
|
*/
|
|
|
|
uint updates;
|
|
|
|
/* Maximum number of connections established per hour. */
|
|
|
|
uint conn_per_hour;
|
|
|
|
/* Maximum number of concurrent connections. */
|
|
|
|
uint user_conn;
|
|
|
|
/*
|
|
|
|
Values of this enum and specified_limits member are used by the
|
|
|
|
parser to store which user limits were specified in GRANT statement.
|
|
|
|
*/
|
|
|
|
enum {QUERIES_PER_HOUR= 1, UPDATES_PER_HOUR= 2, CONNECTIONS_PER_HOUR= 4,
|
|
|
|
USER_CONNECTIONS= 8};
|
|
|
|
uint specified_limits;
|
2002-05-15 12:50:38 +02:00
|
|
|
} USER_RESOURCES;
|
|
|
|
|
2004-12-29 18:30:37 +01:00
|
|
|
|
|
|
|
/*
|
|
|
|
This structure is used for counting resources consumed and for checking
|
|
|
|
them against specified user limits.
|
|
|
|
*/
|
2002-02-01 14:40:38 +01:00
|
|
|
typedef struct user_conn {
|
2004-12-29 18:30:37 +01:00
|
|
|
/*
|
|
|
|
Pointer to user+host key (pair separated by '\0') defining the entity
|
|
|
|
for which resources are counted (By default it is user account thus
|
|
|
|
priv_user/priv_host pair is used. If --old-style-user-limits option
|
|
|
|
is enabled, resources are counted for each user+host separately).
|
|
|
|
*/
|
|
|
|
char *user;
|
|
|
|
/* Pointer to host part of the key. */
|
|
|
|
char *host;
|
2007-10-16 22:11:50 +02:00
|
|
|
/**
|
2007-07-30 10:33:50 +02:00
|
|
|
The moment of time when per hour counters were reset last time
|
|
|
|
(i.e. start of "hour" for conn_per_hour, updates, questions counters).
|
|
|
|
*/
|
|
|
|
ulonglong reset_utime;
|
2004-12-29 18:30:37 +01:00
|
|
|
/* Total length of the key. */
|
|
|
|
uint len;
|
|
|
|
/* Current amount of concurrent connections for this account. */
|
|
|
|
uint connections;
|
|
|
|
/*
|
|
|
|
Current number of connections per hour, number of updating statements
|
|
|
|
per hour and total number of statements per hour for this account.
|
|
|
|
*/
|
|
|
|
uint conn_per_hour, updates, questions;
|
|
|
|
/* Maximum amount of resources which account is allowed to consume. */
|
2002-05-15 12:50:38 +02:00
|
|
|
USER_RESOURCES user_resources;
|
|
|
|
} USER_CONN;
|
2004-12-29 18:30:37 +01:00
|
|
|
|
2000-07-31 21:29:14 +02:00
|
|
|
/* Bits in form->update */
|
|
|
|
#define REG_MAKE_DUPP 1 /* Make a copy of record when read */
|
|
|
|
#define REG_NEW_RECORD 2 /* Write a new record if not found */
|
|
|
|
#define REG_UPDATE 4 /* Uppdate record */
|
|
|
|
#define REG_DELETE 8 /* Delete found record */
|
2004-03-17 19:28:26 +01:00
|
|
|
#define REG_PROG 16 /* User is updating database */
|
2000-07-31 21:29:14 +02:00
|
|
|
#define REG_CLEAR_AFTER_WRITE 32
|
|
|
|
#define REG_MAY_BE_UPDATED 64
|
|
|
|
#define REG_AUTO_UPDATE 64 /* Used in D-forms for scroll-tables */
|
|
|
|
#define REG_OVERWRITE 128
|
2001-11-06 23:13:29 +01:00
|
|
|
#define REG_SKIP_DUP 256
|
2000-07-31 21:29:14 +02:00
|
|
|
|
|
|
|
/* Bits in form->status */
|
|
|
|
#define STATUS_NO_RECORD (1+2) /* Record isn't usably */
|
|
|
|
#define STATUS_GARBAGE 1
|
2001-09-27 20:45:48 +02:00
|
|
|
#define STATUS_NOT_FOUND 2 /* No record in database when needed */
|
2000-07-31 21:29:14 +02:00
|
|
|
#define STATUS_NO_PARENT 4 /* Parent record wasn't found */
|
|
|
|
#define STATUS_NOT_READ 8 /* Record isn't read */
|
|
|
|
#define STATUS_UPDATED 16 /* Record is updated by formula */
|
2000-11-20 01:57:02 +01:00
|
|
|
#define STATUS_NULL_ROW 32 /* table->null_row is set */
|
2001-06-15 04:03:15 +02:00
|
|
|
#define STATUS_DELETED 64
|
WL#3146 "less locking in auto_increment":
this is a cleanup patch for our current auto_increment handling:
new names for auto_increment variables in THD, new methods to manipulate them
(see sql_class.h), some move into handler::, causing less backup/restore
work when executing substatements.
This makes the logic hopefully clearer, less work is is needed in
mysql_insert().
By cleaning up, using different variables for different purposes (instead
of one for 3 things...), we fix those bugs, which someone may want to fix
in 5.0 too:
BUG#20339 "stored procedure using LAST_INSERT_ID() does not replicate
statement-based"
BUG#20341 "stored function inserting into one auto_increment puts bad
data in slave"
BUG#19243 "wrong LAST_INSERT_ID() after ON DUPLICATE KEY UPDATE"
(now if a row is updated, LAST_INSERT_ID() will return its id)
and re-fixes:
BUG#6880 "LAST_INSERT_ID() value changes during multi-row INSERT"
(already fixed differently by Ramil in 4.1)
Test of documented behaviour of mysql_insert_id() (there was no test).
The behaviour changes introduced are:
- LAST_INSERT_ID() now returns "the first autogenerated auto_increment value
successfully inserted", instead of "the first autogenerated auto_increment
value if any row was successfully inserted", see auto_increment.test.
Same for mysql_insert_id(), see mysql_client_test.c.
- LAST_INSERT_ID() returns the id of the updated row if ON DUPLICATE KEY
UPDATE, see auto_increment.test. Same for mysql_insert_id(), see
mysql_client_test.c.
- LAST_INSERT_ID() does not change if no autogenerated value was successfully
inserted (it used to then be 0), see auto_increment.test.
- if in INSERT SELECT no autogenerated value was successfully inserted,
mysql_insert_id() now returns the id of the last inserted row (it already
did this for INSERT VALUES), see mysql_client_test.c.
- if INSERT SELECT uses LAST_INSERT_ID(X), mysql_insert_id() now returns X
(it already did this for INSERT VALUES), see mysql_client_test.c.
- NDB now behaves like other engines wrt SET INSERT_ID: with INSERT IGNORE,
the id passed in SET INSERT_ID is re-used until a row succeeds; SET INSERT_ID
influences not only the first row now.
Additionally, when unlocking a table we check that the thread is not keeping
a next_insert_id (as the table is unlocked that id is potentially out-of-date);
forgetting about this next_insert_id is done in a new
handler::ha_release_auto_increment().
Finally we prepare for engines capable of reserving finite-length intervals
of auto_increment values: we store such intervals in THD. The next step
(to be done by the replication team in 5.1) is to read those intervals from
THD and actually store them in the statement-based binary log. NDB
will be a good engine to test that.
2006-07-09 17:52:19 +02:00
|
|
|
|
|
|
|
/*
|
|
|
|
Such interval is "discrete": it is the set of
|
|
|
|
{ auto_inc_interval_min + k * increment,
|
|
|
|
0 <= k <= (auto_inc_interval_values-1) }
|
|
|
|
Where "increment" is maintained separately by the user of this class (and is
|
|
|
|
currently only thd->variables.auto_increment_increment).
|
|
|
|
It mustn't derive from Sql_alloc, because SET INSERT_ID needs to
|
|
|
|
allocate memory which must stay allocated for use by the next statement.
|
|
|
|
*/
|
|
|
|
class Discrete_interval {
|
|
|
|
private:
|
|
|
|
ulonglong interval_min;
|
|
|
|
ulonglong interval_values;
|
|
|
|
ulonglong interval_max; // excluded bound. Redundant.
|
|
|
|
public:
|
|
|
|
Discrete_interval *next; // used when linked into Discrete_intervals_list
|
|
|
|
void replace(ulonglong start, ulonglong val, ulonglong incr)
|
|
|
|
{
|
|
|
|
interval_min= start;
|
|
|
|
interval_values= val;
|
|
|
|
interval_max= (val == ULONGLONG_MAX) ? val : start + val * incr;
|
|
|
|
}
|
|
|
|
Discrete_interval(ulonglong start, ulonglong val, ulonglong incr) :
|
|
|
|
next(NULL) { replace(start, val, incr); };
|
|
|
|
Discrete_interval() : next(NULL) { replace(0, 0, 0); };
|
|
|
|
ulonglong minimum() const { return interval_min; };
|
|
|
|
ulonglong values() const { return interval_values; };
|
|
|
|
ulonglong maximum() const { return interval_max; };
|
|
|
|
/*
|
|
|
|
If appending [3,5] to [1,2], we merge both in [1,5] (they should have the
|
|
|
|
same increment for that, user of the class has to ensure that). That is
|
|
|
|
just a space optimization. Returns 0 if merge succeeded.
|
|
|
|
*/
|
|
|
|
bool merge_if_contiguous(ulonglong start, ulonglong val, ulonglong incr)
|
|
|
|
{
|
|
|
|
if (interval_max == start)
|
|
|
|
{
|
|
|
|
if (val == ULONGLONG_MAX)
|
|
|
|
{
|
|
|
|
interval_values= interval_max= val;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
interval_values+= val;
|
|
|
|
interval_max= start + val * incr;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
return 1;
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
/* List of Discrete_interval objects */
|
|
|
|
class Discrete_intervals_list {
|
|
|
|
private:
|
|
|
|
Discrete_interval *head;
|
|
|
|
Discrete_interval *tail;
|
|
|
|
/*
|
|
|
|
When many intervals are provided at the beginning of the execution of a
|
|
|
|
statement (in a replication slave or SET INSERT_ID), "current" points to
|
|
|
|
the interval being consumed by the thread now (so "current" goes from
|
|
|
|
"head" to "tail" then to NULL).
|
|
|
|
*/
|
|
|
|
Discrete_interval *current;
|
|
|
|
uint elements; // number of elements
|
2008-06-19 20:47:59 +02:00
|
|
|
void set_members(Discrete_interval *h, Discrete_interval *t,
|
|
|
|
Discrete_interval *c, uint el)
|
|
|
|
{
|
|
|
|
head= h;
|
|
|
|
tail= t;
|
|
|
|
current= c;
|
|
|
|
elements= el;
|
BUG#33029 5.0 to 5.1 replication fails on dup key when inserting
using a trig in SP
For all 5.0 and up to 5.1.12 exclusive, when a stored routine or
trigger caused an INSERT into an AUTO_INCREMENT column, the
generated AUTO_INCREMENT value should not be written into the
binary log, which means if a statement does not generate
AUTO_INCREMENT value itself, there will be no Intvar event (SET
INSERT_ID) associated with it even if one of the stored routine
or trigger caused generation of such a value. And meanwhile, when
executing a stored routine or trigger, it would ignore the
INSERT_ID value even if there is a INSERT_ID value available set
by a SET INSERT_ID statement.
Starting from MySQL 5.1.12, the generated AUTO_INCREMENT value is
written into the binary log, and the value will be used if
available when executing the stored routine or trigger.
Prior fix of this bug in MySQL 5.0 and prior MySQL 5.1.12
(referenced as the buggy versions in the text below), when a
statement that generates AUTO_INCREMENT value by the top
statement was executed in the body of a SP, all statements in the
SP after this statement would be treated as if they had generated
AUTO_INCREMENT by the top statement. When a statement that did
not generate AUTO_INCREMENT value by the top statement but by a
function/trigger called by it, an erroneous Intvar event would be
associated with the statement, this erroneous INSERT_ID value
wouldn't cause problem when replicating between masters and
slaves of 5.0.x or prior 5.1.12, because the erroneous INSERT_ID
value was not used when executing functions/triggers. But when
replicating from buggy versions to 5.1.12 or newer, which will
use the INSERT_ID value in functions/triggers, the erroneous
value will be used, which would cause duplicate entry error and
cause the slave to stop.
The patch for 5.1 fixed it to ignore the SET INSERT_ID value when
executing functions/triggers if it is replicating from a master
of buggy versions, another patch for 5.0 fixed it not to generate
the erroneous Intvar event.
2008-03-14 04:35:41 +01:00
|
|
|
}
|
2008-06-19 20:47:59 +02:00
|
|
|
void operator=(Discrete_intervals_list &); /* prevent use of these */
|
|
|
|
Discrete_intervals_list(const Discrete_intervals_list &);
|
|
|
|
|
WL#3146 "less locking in auto_increment":
this is a cleanup patch for our current auto_increment handling:
new names for auto_increment variables in THD, new methods to manipulate them
(see sql_class.h), some move into handler::, causing less backup/restore
work when executing substatements.
This makes the logic hopefully clearer, less work is is needed in
mysql_insert().
By cleaning up, using different variables for different purposes (instead
of one for 3 things...), we fix those bugs, which someone may want to fix
in 5.0 too:
BUG#20339 "stored procedure using LAST_INSERT_ID() does not replicate
statement-based"
BUG#20341 "stored function inserting into one auto_increment puts bad
data in slave"
BUG#19243 "wrong LAST_INSERT_ID() after ON DUPLICATE KEY UPDATE"
(now if a row is updated, LAST_INSERT_ID() will return its id)
and re-fixes:
BUG#6880 "LAST_INSERT_ID() value changes during multi-row INSERT"
(already fixed differently by Ramil in 4.1)
Test of documented behaviour of mysql_insert_id() (there was no test).
The behaviour changes introduced are:
- LAST_INSERT_ID() now returns "the first autogenerated auto_increment value
successfully inserted", instead of "the first autogenerated auto_increment
value if any row was successfully inserted", see auto_increment.test.
Same for mysql_insert_id(), see mysql_client_test.c.
- LAST_INSERT_ID() returns the id of the updated row if ON DUPLICATE KEY
UPDATE, see auto_increment.test. Same for mysql_insert_id(), see
mysql_client_test.c.
- LAST_INSERT_ID() does not change if no autogenerated value was successfully
inserted (it used to then be 0), see auto_increment.test.
- if in INSERT SELECT no autogenerated value was successfully inserted,
mysql_insert_id() now returns the id of the last inserted row (it already
did this for INSERT VALUES), see mysql_client_test.c.
- if INSERT SELECT uses LAST_INSERT_ID(X), mysql_insert_id() now returns X
(it already did this for INSERT VALUES), see mysql_client_test.c.
- NDB now behaves like other engines wrt SET INSERT_ID: with INSERT IGNORE,
the id passed in SET INSERT_ID is re-used until a row succeeds; SET INSERT_ID
influences not only the first row now.
Additionally, when unlocking a table we check that the thread is not keeping
a next_insert_id (as the table is unlocked that id is potentially out-of-date);
forgetting about this next_insert_id is done in a new
handler::ha_release_auto_increment().
Finally we prepare for engines capable of reserving finite-length intervals
of auto_increment values: we store such intervals in THD. The next step
(to be done by the replication team in 5.1) is to read those intervals from
THD and actually store them in the statement-based binary log. NDB
will be a good engine to test that.
2006-07-09 17:52:19 +02:00
|
|
|
public:
|
|
|
|
Discrete_intervals_list() : head(NULL), current(NULL), elements(0) {};
|
|
|
|
void empty_no_free()
|
|
|
|
{
|
2008-06-19 20:47:59 +02:00
|
|
|
set_members(NULL, NULL, NULL, 0);
|
WL#3146 "less locking in auto_increment":
this is a cleanup patch for our current auto_increment handling:
new names for auto_increment variables in THD, new methods to manipulate them
(see sql_class.h), some move into handler::, causing less backup/restore
work when executing substatements.
This makes the logic hopefully clearer, less work is is needed in
mysql_insert().
By cleaning up, using different variables for different purposes (instead
of one for 3 things...), we fix those bugs, which someone may want to fix
in 5.0 too:
BUG#20339 "stored procedure using LAST_INSERT_ID() does not replicate
statement-based"
BUG#20341 "stored function inserting into one auto_increment puts bad
data in slave"
BUG#19243 "wrong LAST_INSERT_ID() after ON DUPLICATE KEY UPDATE"
(now if a row is updated, LAST_INSERT_ID() will return its id)
and re-fixes:
BUG#6880 "LAST_INSERT_ID() value changes during multi-row INSERT"
(already fixed differently by Ramil in 4.1)
Test of documented behaviour of mysql_insert_id() (there was no test).
The behaviour changes introduced are:
- LAST_INSERT_ID() now returns "the first autogenerated auto_increment value
successfully inserted", instead of "the first autogenerated auto_increment
value if any row was successfully inserted", see auto_increment.test.
Same for mysql_insert_id(), see mysql_client_test.c.
- LAST_INSERT_ID() returns the id of the updated row if ON DUPLICATE KEY
UPDATE, see auto_increment.test. Same for mysql_insert_id(), see
mysql_client_test.c.
- LAST_INSERT_ID() does not change if no autogenerated value was successfully
inserted (it used to then be 0), see auto_increment.test.
- if in INSERT SELECT no autogenerated value was successfully inserted,
mysql_insert_id() now returns the id of the last inserted row (it already
did this for INSERT VALUES), see mysql_client_test.c.
- if INSERT SELECT uses LAST_INSERT_ID(X), mysql_insert_id() now returns X
(it already did this for INSERT VALUES), see mysql_client_test.c.
- NDB now behaves like other engines wrt SET INSERT_ID: with INSERT IGNORE,
the id passed in SET INSERT_ID is re-used until a row succeeds; SET INSERT_ID
influences not only the first row now.
Additionally, when unlocking a table we check that the thread is not keeping
a next_insert_id (as the table is unlocked that id is potentially out-of-date);
forgetting about this next_insert_id is done in a new
handler::ha_release_auto_increment().
Finally we prepare for engines capable of reserving finite-length intervals
of auto_increment values: we store such intervals in THD. The next step
(to be done by the replication team in 5.1) is to read those intervals from
THD and actually store them in the statement-based binary log. NDB
will be a good engine to test that.
2006-07-09 17:52:19 +02:00
|
|
|
}
|
|
|
|
void empty()
|
|
|
|
{
|
|
|
|
for (Discrete_interval *i= head; i;)
|
|
|
|
{
|
|
|
|
Discrete_interval *next= i->next;
|
|
|
|
delete i;
|
|
|
|
i= next;
|
|
|
|
}
|
|
|
|
empty_no_free();
|
|
|
|
}
|
2008-06-19 20:47:59 +02:00
|
|
|
void copy_shallow(const Discrete_intervals_list * dli)
|
|
|
|
{
|
|
|
|
head= dli->get_head();
|
|
|
|
tail= dli->get_tail();
|
|
|
|
current= dli->get_current();
|
|
|
|
elements= dli->nb_elements();
|
|
|
|
}
|
|
|
|
void swap (Discrete_intervals_list * dli)
|
|
|
|
{
|
|
|
|
Discrete_interval *h, *t, *c;
|
|
|
|
uint el;
|
|
|
|
h= dli->get_head();
|
|
|
|
t= dli->get_tail();
|
|
|
|
c= dli->get_current();
|
|
|
|
el= dli->nb_elements();
|
|
|
|
dli->copy_shallow(this);
|
|
|
|
set_members(h, t, c, el);
|
|
|
|
}
|
WL#3146 "less locking in auto_increment":
this is a cleanup patch for our current auto_increment handling:
new names for auto_increment variables in THD, new methods to manipulate them
(see sql_class.h), some move into handler::, causing less backup/restore
work when executing substatements.
This makes the logic hopefully clearer, less work is is needed in
mysql_insert().
By cleaning up, using different variables for different purposes (instead
of one for 3 things...), we fix those bugs, which someone may want to fix
in 5.0 too:
BUG#20339 "stored procedure using LAST_INSERT_ID() does not replicate
statement-based"
BUG#20341 "stored function inserting into one auto_increment puts bad
data in slave"
BUG#19243 "wrong LAST_INSERT_ID() after ON DUPLICATE KEY UPDATE"
(now if a row is updated, LAST_INSERT_ID() will return its id)
and re-fixes:
BUG#6880 "LAST_INSERT_ID() value changes during multi-row INSERT"
(already fixed differently by Ramil in 4.1)
Test of documented behaviour of mysql_insert_id() (there was no test).
The behaviour changes introduced are:
- LAST_INSERT_ID() now returns "the first autogenerated auto_increment value
successfully inserted", instead of "the first autogenerated auto_increment
value if any row was successfully inserted", see auto_increment.test.
Same for mysql_insert_id(), see mysql_client_test.c.
- LAST_INSERT_ID() returns the id of the updated row if ON DUPLICATE KEY
UPDATE, see auto_increment.test. Same for mysql_insert_id(), see
mysql_client_test.c.
- LAST_INSERT_ID() does not change if no autogenerated value was successfully
inserted (it used to then be 0), see auto_increment.test.
- if in INSERT SELECT no autogenerated value was successfully inserted,
mysql_insert_id() now returns the id of the last inserted row (it already
did this for INSERT VALUES), see mysql_client_test.c.
- if INSERT SELECT uses LAST_INSERT_ID(X), mysql_insert_id() now returns X
(it already did this for INSERT VALUES), see mysql_client_test.c.
- NDB now behaves like other engines wrt SET INSERT_ID: with INSERT IGNORE,
the id passed in SET INSERT_ID is re-used until a row succeeds; SET INSERT_ID
influences not only the first row now.
Additionally, when unlocking a table we check that the thread is not keeping
a next_insert_id (as the table is unlocked that id is potentially out-of-date);
forgetting about this next_insert_id is done in a new
handler::ha_release_auto_increment().
Finally we prepare for engines capable of reserving finite-length intervals
of auto_increment values: we store such intervals in THD. The next step
(to be done by the replication team in 5.1) is to read those intervals from
THD and actually store them in the statement-based binary log. NDB
will be a good engine to test that.
2006-07-09 17:52:19 +02:00
|
|
|
const Discrete_interval* get_next()
|
|
|
|
{
|
|
|
|
Discrete_interval *tmp= current;
|
|
|
|
if (current != NULL)
|
|
|
|
current= current->next;
|
|
|
|
return tmp;
|
|
|
|
}
|
|
|
|
~Discrete_intervals_list() { empty(); };
|
|
|
|
bool append(ulonglong start, ulonglong val, ulonglong incr);
|
BUG#33029 5.0 to 5.1 replication fails on dup key when inserting
using a trig in SP
For all 5.0 and up to 5.1.12 exclusive, when a stored routine or
trigger caused an INSERT into an AUTO_INCREMENT column, the
generated AUTO_INCREMENT value should not be written into the
binary log, which means if a statement does not generate
AUTO_INCREMENT value itself, there will be no Intvar event (SET
INSERT_ID) associated with it even if one of the stored routine
or trigger caused generation of such a value. And meanwhile, when
executing a stored routine or trigger, it would ignore the
INSERT_ID value even if there is a INSERT_ID value available set
by a SET INSERT_ID statement.
Starting from MySQL 5.1.12, the generated AUTO_INCREMENT value is
written into the binary log, and the value will be used if
available when executing the stored routine or trigger.
Prior fix of this bug in MySQL 5.0 and prior MySQL 5.1.12
(referenced as the buggy versions in the text below), when a
statement that generates AUTO_INCREMENT value by the top
statement was executed in the body of a SP, all statements in the
SP after this statement would be treated as if they had generated
AUTO_INCREMENT by the top statement. When a statement that did
not generate AUTO_INCREMENT value by the top statement but by a
function/trigger called by it, an erroneous Intvar event would be
associated with the statement, this erroneous INSERT_ID value
wouldn't cause problem when replicating between masters and
slaves of 5.0.x or prior 5.1.12, because the erroneous INSERT_ID
value was not used when executing functions/triggers. But when
replicating from buggy versions to 5.1.12 or newer, which will
use the INSERT_ID value in functions/triggers, the erroneous
value will be used, which would cause duplicate entry error and
cause the slave to stop.
The patch for 5.1 fixed it to ignore the SET INSERT_ID value when
executing functions/triggers if it is replicating from a master
of buggy versions, another patch for 5.0 fixed it not to generate
the erroneous Intvar event.
2008-03-14 04:35:41 +01:00
|
|
|
bool append(Discrete_interval *interval);
|
WL#3146 "less locking in auto_increment":
this is a cleanup patch for our current auto_increment handling:
new names for auto_increment variables in THD, new methods to manipulate them
(see sql_class.h), some move into handler::, causing less backup/restore
work when executing substatements.
This makes the logic hopefully clearer, less work is is needed in
mysql_insert().
By cleaning up, using different variables for different purposes (instead
of one for 3 things...), we fix those bugs, which someone may want to fix
in 5.0 too:
BUG#20339 "stored procedure using LAST_INSERT_ID() does not replicate
statement-based"
BUG#20341 "stored function inserting into one auto_increment puts bad
data in slave"
BUG#19243 "wrong LAST_INSERT_ID() after ON DUPLICATE KEY UPDATE"
(now if a row is updated, LAST_INSERT_ID() will return its id)
and re-fixes:
BUG#6880 "LAST_INSERT_ID() value changes during multi-row INSERT"
(already fixed differently by Ramil in 4.1)
Test of documented behaviour of mysql_insert_id() (there was no test).
The behaviour changes introduced are:
- LAST_INSERT_ID() now returns "the first autogenerated auto_increment value
successfully inserted", instead of "the first autogenerated auto_increment
value if any row was successfully inserted", see auto_increment.test.
Same for mysql_insert_id(), see mysql_client_test.c.
- LAST_INSERT_ID() returns the id of the updated row if ON DUPLICATE KEY
UPDATE, see auto_increment.test. Same for mysql_insert_id(), see
mysql_client_test.c.
- LAST_INSERT_ID() does not change if no autogenerated value was successfully
inserted (it used to then be 0), see auto_increment.test.
- if in INSERT SELECT no autogenerated value was successfully inserted,
mysql_insert_id() now returns the id of the last inserted row (it already
did this for INSERT VALUES), see mysql_client_test.c.
- if INSERT SELECT uses LAST_INSERT_ID(X), mysql_insert_id() now returns X
(it already did this for INSERT VALUES), see mysql_client_test.c.
- NDB now behaves like other engines wrt SET INSERT_ID: with INSERT IGNORE,
the id passed in SET INSERT_ID is re-used until a row succeeds; SET INSERT_ID
influences not only the first row now.
Additionally, when unlocking a table we check that the thread is not keeping
a next_insert_id (as the table is unlocked that id is potentially out-of-date);
forgetting about this next_insert_id is done in a new
handler::ha_release_auto_increment().
Finally we prepare for engines capable of reserving finite-length intervals
of auto_increment values: we store such intervals in THD. The next step
(to be done by the replication team in 5.1) is to read those intervals from
THD and actually store them in the statement-based binary log. NDB
will be a good engine to test that.
2006-07-09 17:52:19 +02:00
|
|
|
ulonglong minimum() const { return (head ? head->minimum() : 0); };
|
|
|
|
ulonglong maximum() const { return (head ? tail->maximum() : 0); };
|
|
|
|
uint nb_elements() const { return elements; }
|
2008-06-19 20:47:59 +02:00
|
|
|
Discrete_interval* get_head() const { return head; };
|
|
|
|
Discrete_interval* get_tail() const { return tail; };
|
|
|
|
Discrete_interval* get_current() const { return current; };
|
WL#3146 "less locking in auto_increment":
this is a cleanup patch for our current auto_increment handling:
new names for auto_increment variables in THD, new methods to manipulate them
(see sql_class.h), some move into handler::, causing less backup/restore
work when executing substatements.
This makes the logic hopefully clearer, less work is is needed in
mysql_insert().
By cleaning up, using different variables for different purposes (instead
of one for 3 things...), we fix those bugs, which someone may want to fix
in 5.0 too:
BUG#20339 "stored procedure using LAST_INSERT_ID() does not replicate
statement-based"
BUG#20341 "stored function inserting into one auto_increment puts bad
data in slave"
BUG#19243 "wrong LAST_INSERT_ID() after ON DUPLICATE KEY UPDATE"
(now if a row is updated, LAST_INSERT_ID() will return its id)
and re-fixes:
BUG#6880 "LAST_INSERT_ID() value changes during multi-row INSERT"
(already fixed differently by Ramil in 4.1)
Test of documented behaviour of mysql_insert_id() (there was no test).
The behaviour changes introduced are:
- LAST_INSERT_ID() now returns "the first autogenerated auto_increment value
successfully inserted", instead of "the first autogenerated auto_increment
value if any row was successfully inserted", see auto_increment.test.
Same for mysql_insert_id(), see mysql_client_test.c.
- LAST_INSERT_ID() returns the id of the updated row if ON DUPLICATE KEY
UPDATE, see auto_increment.test. Same for mysql_insert_id(), see
mysql_client_test.c.
- LAST_INSERT_ID() does not change if no autogenerated value was successfully
inserted (it used to then be 0), see auto_increment.test.
- if in INSERT SELECT no autogenerated value was successfully inserted,
mysql_insert_id() now returns the id of the last inserted row (it already
did this for INSERT VALUES), see mysql_client_test.c.
- if INSERT SELECT uses LAST_INSERT_ID(X), mysql_insert_id() now returns X
(it already did this for INSERT VALUES), see mysql_client_test.c.
- NDB now behaves like other engines wrt SET INSERT_ID: with INSERT IGNORE,
the id passed in SET INSERT_ID is re-used until a row succeeds; SET INSERT_ID
influences not only the first row now.
Additionally, when unlocking a table we check that the thread is not keeping
a next_insert_id (as the table is unlocked that id is potentially out-of-date);
forgetting about this next_insert_id is done in a new
handler::ha_release_auto_increment().
Finally we prepare for engines capable of reserving finite-length intervals
of auto_increment values: we store such intervals in THD. The next step
(to be done by the replication team in 5.1) is to read those intervals from
THD and actually store them in the statement-based binary log. NDB
will be a good engine to test that.
2006-07-09 17:52:19 +02:00
|
|
|
};
|
2009-09-23 23:32:31 +02:00
|
|
|
|
|
|
|
#endif /* STRUCTS_INCLUDED */
|