From: Stewart Smith
Date: July 18 2007 1:15am
Subject: Re: IPV6 data type patch
List-Archive: http://lists.mysql.com/internals/34842
Message-Id: <1184721311.24663.291.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-4vv2V791fcTCvx+8EYcZ"

--=-4vv2V791fcTCvx+8EYcZ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2007-07-17 at 16:05 +0200, Milos Prodanovic wrote:
> I've considered network data types as blob or as a string.

Certainly blob makes more sense. Much more space efficient.

> IPv4 address 192.168.1.1 is internally stored as 4xbyte (or uin32)
> char *ptr=3D"\192\168\1\1"
> and IPv6 address aabb:ccdd:dead:beef:1234:4321:a1b2:c3d4 is internally
> stored as 16xbyte
> char *ptr=3D"\xaa\xbb\xcc\xdd\xde\xad\xbe\xef\12\x34\x43\x21\xa1\xb2\xc3\=
xd4";
>=20
> Data type uses STRING_RESULT as result type, and where charset is needed =
for
> some function, my_charset_bin is used.

Also check behaviour with multibyte character sets and all that... good
way to get a headache and bugs...

> To be able to do my GSoC project and In order to better understand how
> things are done in MySQL I've tried to find and understand code on
> each place that string type or blob type is questioned in the mysql
> code. I've tried to understand what the code is 'doing' and what was
> decision based on mysql type (what are consequences).

great! (this certainly takes time)

> That doesn't mean that I've grasped correctly all occurrences
> correctly, but I can
> post my report file where I've wrote what files was under examination, an=
d what
> I've decided when I was rendering MySQL code. Reports are like "should
> I change it , or should it stay the way it is, and why I've done this
> way". I didn't want to
> put lot of comments on places that I've just inserted "case MYSQL_TYPE_IP=
V6",
> so I've stored comments in separate file.
>=20
> I will try to get closer look on NDBAPI.

I'm not sure I'd spend too much time on it.. but maybe just getting a
bit of an introduction to NDB would be enough... I have a video up on
Google Video
(http://video.google.com.au/url?docid=3D-4567104036778249401&esrc=3Dsr1&ev=
=3Dv&q=3DMySQL%2BCluster&srcurl=3Dhttp%3A%2F%2Fvideo.google.com.au%2Fvideop=
lay%3Fdocid%3D-4567104036778249401&vidurl=3D%2Fvideoplay%3Fdocid%3D-4567104=
036778249401%26q%3DMySQL%2BCluster%26total%3D7%26start%3D0%26num%3D10%26so%=
3D0%26type%3Dsearch%26plindex%3D0&usg=3DAL29H21FpJvqb9Cp4ywSEkCux-aYBhFFlg)

err.. great... just search on google video for "MySQL Cluster".

NDBAPI and a broader understanding of NDB can take a while.


> It would be nice to make some functionality tests, and I'm not sure
> that I can make
> tests of all possible 'use cases', but I'm glad to do tests if you
> have some crucial test
> that could show usability.

i don't have any magic solution for the testing of this with NDB endian
compatibility.


but general testing can be started with mysql-test-run scripts (see
mysql-test/t/*test files)...
--=20
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

--=-4vv2V791fcTCvx+8EYcZ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQIVAwUARp1pn73yNwHyU3DLAQIEjhAAlD4/SFb8tgE3qID2i5xF6Xhyp1S3CeU4
ULiAGsoMOXMYEx9MnSqgC83fSb/5n9TjwUi97yTxxfCMacvlADY5zaPg2HVs6wRg
mTwdJKScRfR+rbNZ15zh7DVaTn43NUAicCSxTFfqQOSgp5WhdopZJMSyl8obMEle
DUolxyNsAM71BW/M0sb4YCk79xc02NThRM2RYZtMbgwXj5B6f0vmsvK+VWBDzt33
wI/qa7BlfUt8K5d1HYUpbV0fv8gGu7xvbUt4QbG6e8PaW/dK+xJJ4PtIPb3rUMJC
iXoraXT/zEEGHKCdX6VY4kZUlEB8m0O/A2gxIVfauqKffF5A8Xm7Fqhypc78mpki
5UP6KkfRxJcALZ9T9dSvOA96oX3dYWc3AT3Sw4wq//lXzv8tGru+bvPuu2gU0lDt
K/Nb4FnkLHXItLeaFFo/2r1KOPbdo0//U0oHttyhqoaTmVHuSTzy53IabIXqlQkP
RDNizN6/akMX9abvvgSiFkwJgsoMgZDynMzzrly0GvbIvaUr4N+9kPF76Hi40K9o
PEuxxYnfgzo65RTVmxGB4OzuK/mZxKilc25IcjuooHJ/O18QYp7wmcTVYaXYY1vT
Wvvm5aN8cUgcFapV7dhu24aX4Ej3ojBMwelncIt42UD8EJBg2X9L5OlBLsioLgtI
Rg4CUWlW/r8=
=WN3j
-----END PGP SIGNATURE-----

--=-4vv2V791fcTCvx+8EYcZ--