An error occurred fetching the project authors.
- 06 Feb, 2005 1 commit
-
-
patg@krsna.patg.net authored
This patch contains all that my previous patch (1.1814) contained, with the addition of using cli_fetch_lengths for handling binary data (Bar noted this on the review of 1.1814, Guilhem suggested using cli_fetch_lenghts by making available via removal of static in method definition and declaration in mysql.h, but Konstantin had some reservations, but he said to commit the patch using this anyway, and I suppose this can be discussed. I abandoned 1.1814 because Monty made a couple fixes to my code as well as formatting changes, and I thought it would just be easier to hand-edit my changes into a fresh clone and then make a patch. The reason for using cli_fetch_lengths is so that I can correctly get the length of the field I am setting into the field. I was previously using 'strlen' but Bar pointed out this won't correctly get the length of binary data and is also less effecient. Upon testing, it was in fact verified that binary data in a blob table was being inserted correctly, but not being retrieved correctly, all due to not having the correct value for the field: (*field)->store(row[x], strlen(row[x]), &my_charset_bin); was changed to: (*field)->store(row[x], lengths[x], &my_charset_bin); lengths being a unsigned long pointer to the values of the field lengths from a MYSQL_ROW. Since the server doesn't have the function "mysql_fetch_lengths" available, I tried to use "result->lengths", but this isn't set, so I finally successfully used cli_fetch_lenghts, which does give the correct lengths, and now the binary data gets retrieved correctly. I've also run the code through indent-ex and am using Brian's vimrc to ensure correct formatting! This code passes the entire test suite, without any errors or warning on both my workstation and build.mysql.com
-
- 04 Feb, 2005 2 commits
-
-
guilhem@mysql.com authored
Proposal to fix this problem: when using libmysqlclient, you must call mysql_server_end() to nicely free memory at the end of your program; it however sounds weird to call a function named *SERVER_end* when you're the CLIENT (you're not ending the server, you're ending your ability to talk to servers). So here I add two defines which should be more generic names. Our manual mentions these functions only for libmysqld API so needs some fixing, and then we can close BUG#8099 and BUG#6149.
-
guilhem@mysql.com authored
Proposal to fix this problem: when using libmysqlclient, you must call mysql_server_end() to nicely free memory at the end of your program; it however sounds weird to call a function named *SERVER_end* when you're the CLIENT (you're not ending the server, you're ending your ability to talk to servers). So here I add two defines which should be more generic names. This was longly discussed with Konstantin, Serg, Brian. The problem started from a post on valgrind-users list: http://sourceforge.net/mailarchive/forum.php?thread_id=5778035&forum_id=32038 ; our manual mentions these functions only for libmysqld API so needs some fixing, and then we can close BUG#8099 and BUG#6149.
-
- 17 Dec, 2004 1 commit
-
-
konstantin@mysql.com authored
-
- 16 Dec, 2004 1 commit
-
-
konstantin@mysql.com authored
fixes. Still to do: - deploy my_strtoll10 in limbysql.c - add mysql_options option to switch MYSQL_DATA_TRUNCATED on and off.
-
- 10 Nov, 2004 1 commit
-
-
bar@mysql.com authored
-
- 08 Nov, 2004 1 commit
-
-
bar@mysql.com authored
Adding a prototype for the new function.
-
- 01 Nov, 2004 1 commit
-
-
konstantin@mysql.com authored
having approval for it since 4.1.4, I also have some assurance that very few people actually used this: to enable these calls a user had to #define HAVE_DEPRECATED_411_API and recompile the client library.
-
- 19 Oct, 2004 1 commit
-
-
monty@mishka.local authored
Simple optimzations and cleanups Removed compiler warnings and fixed portability issues Added client functions 'mysql_embedded()' to allow client to check if we are using embedded server Fixes for purify
-
- 25 Aug, 2004 1 commit
-
-
paul@kite-hub.kitebird.com authored
Fix a misleading plural that should be singular. Fix other typos while I'm at it.
-
- 19 Aug, 2004 1 commit
-
-
pem@mysql.comhem.se authored
-
- 03 Aug, 2004 1 commit
-
-
konstantin@mysql.com authored
- 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.
-
- 22 Jul, 2004 1 commit
-
-
hf@deer.(none) authored
#4700 (Unsigned value returned as signed) just no appropriate checking #4701 (Errors returned earlier than expected) all errors returned from send_command() #4702 (Result isn't freed properly if there's no retrieval) flush_use_result has only 'client' version and should be made 'virtual'
-
- 25 Jun, 2004 2 commits
-
-
monty@mysql.com authored
-
konstantin@mysql.com authored
-
- 24 Jun, 2004 1 commit
-
-
konstantin@mysql.com authored
work (prepared statements)" and after-review fixes: - str_to_TIME renamed to str_to_datetime to pair with str_to_time - functions str_to_time and str_to_TIME moved to sql-common - send_data_str now supports MYSQL_TYPE_TIME, MYSQL_TIME_DATE, MYSQL_TIME_DATETIME types of user input buffers. - few more comments in the client library - a test case added.
-
- 23 Jun, 2004 1 commit
-
-
monty@mysql.com authored
with ALTER TABLE and CREATE/DROP INDEX. (Bug #3109) Make net_buffer_length visible for mysql clients (Bug #4206)
-
- 16 Jun, 2004 1 commit
-
-
konstantin@mysql.com authored
-
- 15 Jun, 2004 1 commit
-
-
guilhem@mysql.com authored
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.
-
- 05 Jun, 2004 1 commit
-
-
konstantin@mysql.com authored
-
- 04 Jun, 2004 1 commit
-
-
konstantin@mysql.com authored
-
- 31 May, 2004 1 commit
-
-
hf@deer.(none) authored
-
- 26 May, 2004 1 commit
-
-
hf@deer.(none) authored
-
- 07 May, 2004 1 commit
-
-
georg@beethoven.local authored
to allow binding of userland functions in PHP.
-
- 01 May, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 30 Apr, 2004 1 commit
-
-
monty@mysql.com authored
Added checking of cut read lines in bootstrap thread (Bug #2874)
-
- 29 Apr, 2004 2 commits
-
-
konstantin@mysql.com authored
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.
-
konstantin@mysql.com authored
requested by Monty for Bug#1647 (No way to determine what size blob/clob is being returned into bound buffer)
-
- 31 Mar, 2004 1 commit
-
-
monty@mysql.com authored
Portability fixes
-
- 28 Mar, 2004 1 commit
-
-
konstantin@mysql.com authored
No need to check for result existence any more, store_result functions now are shorter. cli_read_binary_rows rewritten to handle MYSQL_DATA directly.
-
- 25 Mar, 2004 1 commit
-
-
monty@mysql.com authored
-
- 23 Mar, 2004 1 commit
-
-
jcole@mugatu.jcole.us authored
-
- 18 Mar, 2004 1 commit
-
-
monty@mysql.com authored
Changed _XXX to _MY_XXX to solve conflict problem on Mac OS X
-
- 15 Mar, 2004 1 commit
-
-
konstantin@mysql.com authored
flaws list) TODO: * verify that no sequence of API calls produces SIGSEGV. That is, verify that mysql_stmt_init -> mysql_stmt_fetch is OK, or mysql_stmt_prepare -> mysql_stmt_fetch_column is OK and sets meaningful error. * remove alloc_stmt_fields call * revise stmt->state codes and statement states. * there are other items in prepared statements 'to fix' document. Done: - cleanups and comments - revision of prepared statement error codes. - mysql_stmt_prepare is now can always be called (that is, you can reprepare a statement) - new implementation of mysql_stmt_close and fetch cancellation
-
- 10 Mar, 2004 1 commit
-
-
konstantin@oak.local authored
read_statistic -> read_statistics (statistic is adjective)
-
- 05 Mar, 2004 1 commit
-
-
konstantin@mysql.com authored
Renames: mysql_bind_param -> mysql_stmt_bind_param mysql_bind_result -> mysql_stmt_bind_result mysql_execute -> mysql_stmt_execute mysql_fetch -> mysql_stmt_fetch mysql_fetch_column -> mysql_stmt_fetch_column mysql_get_metadata -> mysql_stmt_result_metadata mysql_param_count -> mysql_stmt_param_count mysql_param_result -> mysql_stmt_param_metadata mysql_prepare -> mysql_stmt_prepare mysql_send_long_data -> mysql_stmt_send_long_data client_test.c cleaned up from memory leaks
-
- 16 Feb, 2004 1 commit
-
-
monty@mysql.com authored
Fixed that blobs >16M can be inserted/updated Fixed bug when doing CREATE TEMPORARY TABLE ... LIKE
-
- 14 Feb, 2004 1 commit
-
-
hf@deer.(none) authored
now it's working
-
- 10 Feb, 2004 2 commits
-
-
dlenev@dlenev.mshome authored
Done clean-up in prep stmt API functions: 1) Removed some checks that were performed only in debug version were making debug version more tolerable to user errors than production (and thus caused problems for example masking some bugs). 2) Also removed some other checks to make prep stmt API consistent with the rest of C API (this also in line with general politics - make checks in only those places where errors are very common and hard to spot).
-
hf@deer.(none) authored
now we execute only one first select during mysql_real_query others - during 'mysql_next_result'
-