Re: GUID storage
Nowhere in this discussion was this question. Is it in the plans to have a 128 bit numeric column type for MySQL? If so, in what kind of time frame? If not, why not? Character arrays are obviously, but they are probably not the best way to get optimal performance. Native support for a 128 bit number, usable as a UUID, would be better. - ray On May 12, 2004, at 3:07 PM, Jeremy Zawodny wrote: On Wed, May 12, 2004 at 02:50:55PM -0700, Larry Lowry wrote: Well I'm trying to move to MySQL from the MS SQL Server world. Most data elements are easy except for the uniqueidentifier. In the MySQL world what is the preferred/best way to store a uniqueidentifier? The easiest would just be a char(36). If you have unique ids that are 36 characters, then use a char(36). That seems like the obvious thing to do. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ [book] High Performance MySQL -- http://highperformancemysql.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
no create/update time for InnoDB from SHOW TABLE STATUS?
It looks as though, when I go into my databases, and use the command SHOW TABLE STATUS, that InnoDB tables do not have some information. I am on MySQL 4.1.0-alpha-debug. Has this been fixed in later versions? Example: mysql show table status; +--+++-++- +-+--+---+ +-+-++--- ++-+ | Name | Type | Row_format | Rows| Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time | Update_time | Check_time | Charset | Create_options | Comment | +--+++-++- +-+--+---+ +-+-++--- ++-+ | cur | InnoDB | Dynamic| 325214 | 2279 | 741294080 | NULL |114163712 | 0 | 337810 | NULL | NULL| NULL | latin1_swedish_ci | pack_keys=1| InnoDB free: 6601728 kB | | old | InnoDB | Dynamic| 1233005 | 10405 | 12830375936 | NULL |455147520 | 0 |1545059 | NULL | NULL| NULL | latin1_swedish_ci | pack_keys=1| InnoDB free: 6601728 kB | +--+++-++- +-+--+---+ +-+-++--- ++-+ 2 rows in set (2.78 sec) Notice the Create_time and Update_time data is NULL. Any reason? thanx - ray -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql_info not very informative?
What is annoying about this is that if you use mysqlimport to put this data into the table, I get: testdb.testtable: Records: 3 Deleted: 0 Skipped: 0 Warnings: 2 So, where are the warnings coming from? Is there some public API, below the C API layer, that one can use to obtain this information? If I do an insert and lose information, and get absolutely no warning about the problem, and no way to determine that there was an information loss, then I could call that a bug. I keep looking for a mysql_warnings function, or maybe a mysql_really_info, and I am not seeing anything else to work with. One can do the data validation at the application level by re-fetching the data, but isn't this the most complicated and ugly way to deal with the problem? The database obviously has the facts. Hence the warning from mysqlimport. Is there a reason it must keep the information to itself? - ray On Saturday, August 2, 2003, at 5:24AM, Adam Fortuno wrote: Actually, MySQL doesn't normally give overrun cut-off information (best I know). Use MySQL 4.0.x on 10.2.6, and MySQL has always performed that way. Regards, A$ On Friday, August 1, 2003, at 05:37 PM, Ray Kiddy wrote: I am trying to insert data using the C API. Particulars: OS: Mac OS X 10.3 (7A179) MySQL: MySQL 4.1.0-alpha table type: tried both MyISAM and InnoDB I have a table: mysql describe testtable; ++-+---+--+-+- +---+ | Field | Type| Collation | Null | Key | Default | Extra | ++-+---+--+-+- +---+ | _PK| int(11) | binary| | PRI | 0 | | | first | char(3) | latin1_swedish_ci | YES | | NULL| | | second | char(3) | latin1_swedish_ci | YES | | NULL| | | third | char(3) | latin1_swedish_ci | YES | | NULL| | ++-+---+--+-+- +---+ 4 rows in set (0.00 sec) Note that the first, second, and third columns have 3 characters of space. When I do: printf(insert: %s\n, insert); int result = mysql_query(one, insert); printf(info: %s\n, mysql_info(one)); I get: insert: INSERT INTO testtable (_PK,first,second,third) VALUES (1,'AAAXXX','BBB','CCC') info: (null) insert: INSERT INTO testtable (_PK,first,second,third) VALUES (2,'DDD','EEE','FFF') info: (null) insert: INSERT INTO testtable (_PK,first,second,third) VALUES (3,'GGG','HHHXXX','III') info: (null) Note that the value in the first insert, 'AAAXXX', is too long to fit. As is 'HHHXXX' in the third insert. And indeed, I see: mysql select * from testtable; +-+---++---+ | _PK | first | second | third | +-+---++---+ | 1 | AAA | BBB| CCC | | 2 | DDD | EEE| FFF | | 3 | GGG | HHH| III | +-+---++---+ 3 rows in set (0.00 sec) So, why is mysql_info not giving me any information about the data loss that is going on here? Is that not information that might be of interest? Is there some other call I have to make that will prepare for the mysql_info call? The doc does not seem to indicate this, but one never knows. thanx - ray -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql_info not very informative?
I am trying to insert data using the C API. Particulars: OS: Mac OS X 10.3 (7A179) MySQL: MySQL 4.1.0-alpha table type: tried both MyISAM and InnoDB I have a table: mysql describe testtable; ++-+---+--+-+-+---+ | Field | Type| Collation | Null | Key | Default | Extra | ++-+---+--+-+-+---+ | _PK| int(11) | binary| | PRI | 0 | | | first | char(3) | latin1_swedish_ci | YES | | NULL| | | second | char(3) | latin1_swedish_ci | YES | | NULL| | | third | char(3) | latin1_swedish_ci | YES | | NULL| | ++-+---+--+-+-+---+ 4 rows in set (0.00 sec) Note that the first, second, and third columns have 3 characters of space. When I do: printf(insert: %s\n, insert); int result = mysql_query(one, insert); printf(info: %s\n, mysql_info(one)); I get: insert: INSERT INTO testtable (_PK,first,second,third) VALUES (1,'AAAXXX','BBB','CCC') info: (null) insert: INSERT INTO testtable (_PK,first,second,third) VALUES (2,'DDD','EEE','FFF') info: (null) insert: INSERT INTO testtable (_PK,first,second,third) VALUES (3,'GGG','HHHXXX','III') info: (null) Note that the value in the first insert, 'AAAXXX', is too long to fit. As is 'HHHXXX' in the third insert. And indeed, I see: mysql select * from testtable; +-+---++---+ | _PK | first | second | third | +-+---++---+ | 1 | AAA | BBB| CCC | | 2 | DDD | EEE| FFF | | 3 | GGG | HHH| III | +-+---++---+ 3 rows in set (0.00 sec) So, why is mysql_info not giving me any information about the data loss that is going on here? Is that not information that might be of interest? Is there some other call I have to make that will prepare for the mysql_info call? The doc does not seem to indicate this, but one never knows. thanx - ray -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
additions to mysqlimport?
Hello - I am curious what extensions to mysqlimport people might be interested in seeing. I am importing some data with inconsistencies and and I find that mysqlimport helps one not at all. It seems to me that there are things it could do. For example: -rejected_lines=filename : would put all lines that generated errors or warnings in a separate file. --verbose : it could actually be verbose and list out all warnings and errors. I know this is a shocking suggestion, but hey, let's be bold. --no_insert : this would allow one to pre-flight data without actually causing the insert to happen, as -n does for make. --lines-commented-out-by=... : pretty obvious --terminate-on=word : deleted, skipped, or warning, for example, if you want to stop if there is even one warning. Any other ideas? I am thinking of trying to extend it myself and am open to suggestions. thanx - ray - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL 4.0.7 is released
What does it mean when you say: MySQL 4.0.7 is released and then you give a URL? When one goes to the URL, one sees text which says the latest version is 4.0.5. So, is 4.0.7 released or is it not? If so, why do you not point to pages on the web site which actually include the release which you are announcing? For example, since http://www.mysql.com/downloads/ does not point to the 4.0.7 version, which page does? thanx - ray On Friday, December 27, 2002, at 12:10 PM, Lenz Grimmer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, MySQL 4.0.7, a new version of the popular Open Source Database, has been released. It is now available in source and binary form for a number of platforms from our download pages at http://www.mysql.com/downloads/ and mirror sites. snip - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
read-only... even after myisamchk -ru
I had used MySQL's myisampack utility to pack my tables, which makes them read-only, but now I want them to be write-able again. I have used myisamchk --recover --unpack (tried -ru as well) and the table is still read-only. What is the actual incantation one must use here? I can backup and re-create the table, but that seems unnecessary, if the documentation on myisamchk is correct thanx - ray - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
tools for characterizing performance?
It seems strange to me that the tools in the MySQL distribution that let you run automatic performance tests rely on DBI and perl. If I want to test the performance of MySQL, why is it a good idea to do this while relying on another technology, one that is distributed by someone else, one that may have integration issues with pre-release versions of MySQL? I imagine that the perl part of this makes it easier to generate those nice little reports. So, why would one not use MySQL tools to run the performance tests and dump out to a raw format, which would then be fed into a completely separate application, written in perl for example, that would then pretty-print the data? This would seem to be a much less fragile solution. It would also have the benefit that one could test the performance of MySQL without polluting the results with perl and DBI cruft. Would anybody care to defend the current approach? thanx - ray - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
why so late with Mac OS X versions?
Can someone tell me what the holdup is in getting binaries built for Mac OS X? I notice on the www.mysql.com web page that the latest version of the binaries available of the is 4.0.3. Why is this? If somebody can point to the cause of the logjam, there might be something I can do about it. Is it a technical, resource or a personnel problem? thanx - ray - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
[Bug] compile problem on Mac OS X 10.2
A number of people have asked about this, and some have figured it out and posted info somewhere, but not in the www.mysql.com docs. Perhaps, I need to report it on this list for it to get into a distro, yes? In configure, there is a bit that starts at line 7514: *darwin*) if test $ac_cv_c_compiler_gnu = yes then CFLAGS=$CFLAGS -traditional-cpp -DHAVE_DARWIN_THREADS -D_P1003_1B_VISIBLE -DSIGNAL_WITH_VIO_CLOSE -DSIGNALS_DONT_ BREAK_READ -DHAVE_BROKEN_REALPATH CXXFLAGS=$CXXFLAGS -traditional-cpp -DHAVE_DARWIN_THREADS -D_P1003_1B_VISIBLE -DSIGNAL_WITH_VIO_CLOSE -DSIGNALS_D ONT_BREAK_READ MAX_C_OPTIMIZE=-O with_named_curses= fi ;; Change: with_named_curses= to: with_named_curses=-ltermcap ... and then it builds. Voila! Note, this is for Mac OS X 10.2, and not earlier Mac OS X systems. thanx - ray - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Won't compile on Mac OS X 10.2
I got MySQL 4.0.2-alpha compiled on Mac OS X 10.2 (final version - Jaguar6C115). I am having problems with getting any client to connect to it, so perhaps I am doing something else wrong, which is possible since I am new to MySQL First I tried: ./configure --with-named-curses-libs=/usr/lib/libncurses.dylib This did not work. Then I manually executed the one compile that was failing, adding the libncurses.dylib to the list of libraries to use, as such: g++ -O3 -DDBUG_OFF -fno-implicit-templates -fno-exceptions -fno-rtti -traditional-cpp -DHAVE_DARWIN_THREADS -D_P1003_1B_ VISIBLE -DSIGNAL_WITH_VIO_CLOSE -DSIGNALS_DONT_BREAK_READ -o mysql mysql.o readline.o sql_string.o completion_hash.o ../ readline/libreadline.a ../libmysql/.libs/libmysqlclient.a /usr/lib/libncurses.dylib -lz -lm -lz -lm Then I did a make again and everything went along to the end. For some reason my client sub-directory did not get re-named to bin and, as I said, I cannot connect. Keep getting: % mysql ERROR 2002: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) ... so I may have messed something up. Maybe someone else, with more experience with installing, can pick the ball up and move it along... thanx - ray On Sunday, August 25, 2002, at 05:39 PM, Mitch Leung wrote: Dear Sir, MySQL 3.23.52 won't compile on Mac OS X 10.2 based on Darwin 6.0 which comes pre-installed with gcc 3.1 I don't want to uninstall it as it would probably bring down other major functions of the new system. Regards, Mitch Leung - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
