-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Folk, I am studying about the usage of "mysql_type" and "pgsql_type" from Schema API. It seems that let us able to select different data type for different database backend. Basically, it seems to be a great idea ;-) BTW, I don't understand why we need it in locale.install. {locales_source}.source and {locales_target}.translation both map TEXT for other database (says, we only have pgsql in case of D6), but map MySQL into BLOB. Do we have any special reason for this different handling? In case of PostgreSQL, decode BLOB require a manual call for db_decode_blob(); BTW, db_decode_blob() for MySQL is just a dummy... According to different data type mapping, application level should also change their implementation... Any idea about the detail story of this issue? Is this even a bug? If so I would like to give some effort based on this issue. Thanks ;-) Regard - -- Edison Wong hswong3i@gmail.com http://edin.no-ip.com/html/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHnE6lBPIQaq+ZRd8RAll9AKC+cUfHzjtDNFuhTkGg72Kr0SXp9wCcCDKT 1Ij9sf8T/KzMZDvTWtmIc3A= =IsO3 -----END PGP SIGNATURE-----