On Mon, 2007-07-16 at 06:04 +0000, Milos Prodanovic wrote:
> Down below you can find IPV6 data type patch, as result of Google Summer of Code
> midterm milestone.
Disclaimer: I haven't read through the whole patch.
One thing to consider is endian compatibility.
On disk format (for local disk engines) should be compatible... is this
so? are you always storing these types in network byte order (surely the
simplest)?
This extends into more fun for NDB with the endian compatibility
patches. I've CC'd David who's been working on this.
For NDB with endian compatibility... a SQL node could store a value into
the cluster and an SQL node with a different byte order could read it..
The value should, of course, make sense to the other node.
David can probably better comment.... this is possibly the same issue
with GIS data for NDB.
Also, a spec of how things are stored would be great - means that people
should be able to use the IP types in a compatible way from NDBAPI
applications (which have no MySQL Server code in them... so a data type
added inside the SQL server is unknown to an NDB API application).
--
Stewart Smith, Senior Software Engineer
MySQL AB, www.mysql.com
Office: +14082136540 Ext: 6616
VoIP: 6616@stripped
Mobile: +61 4 3 8844 332
Jumpstart your cluster:
http://www.mysql.com/consulting/packaged/cluster.html
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
