From: Date: January 1 1970 12:59am Subject: Re: GUID storage List-Archive: http://lists.mysql.com/mysql/168061 Message-Id: MIME-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit From: Ray Kiddy 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! > | 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/mysql?unsub=ray@stripped >