In the last episode (Jun 28), Ray Kiddy said:
> 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?
I don't know of any 32-bit compiler that provides a 128-bit integer
type, which means for most platforms mysql would have to req
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 nu
Hi!
On May 12, Larry Lowry wrote:
> A uniqueidentifier in MS SQL is basically a guid. I am generating
> them via System.Guid.NewGuid().ToString(N") in the Dot Net
> framework which now returns me a string of 32 characters (hex).
> Internally I understand it is a 128-bit integer. As an option I
In the last episode (May 12), Larry Lowry said:
> A uniqueidentifier in MS SQL is basically a guid. I am generating
> them via System.Guid.NewGuid().ToString(N") in the Dot Net
> framework which now returns me a string of 32 characters (hex).
> Internally I understand it is a 128-bit integer. As
TED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, May 12, 2004 3:10 PM
Subject: Re: GUID storage
> In the last episode (May 12), Larry Lowry said:
> > Well I'm trying to move to MySQL from the MS SQL Server world. Most
> > data elements are easy except for the uniqueidentif
In the last episode (May 12), Larry Lowry said:
> 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
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
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).
Thanks.
Larry Lowry
In this case I
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).
Thanks.
Larry Lowry
