Originally, the NATIVE postgresql driver was (somewhat?) ANSI ST incompatible. I had it working in VAST. Along the way, the Cryptography package was added as a dependency to support MD5 passwords. If #hex is not ANSI ST, then the postgres native driver is likely unaffected by changes to #hex, other than its effect on MD5. I can verify this later today. -- Yanni Mariano Martinez Peck wrote:
On Tue, Jul 20, 2010 at 2:46 AM, Henrik Johansen <henrik.s.johansen@veloxit.no <mailto:henrik.s.johansen@veloxit.no>> wrote:
Iirc, it was reintroduced in Pharo in relation to SqueakDBX, might want to check with Mariano that changes will be compatible/SqueakDBX is updated.
Hi Henrik. Indeed, it was included for SqueakDBX. Actually, not for itself, but the NATIVE postgresql driver used to depends in the chripto package. Then, the MD5 class was put in PharoCore so it didn't depend anymore. But the hex was missing. Now...if you ask me if this change will affect the postgres native driver, I HAVE NO IDEA. The only thing I can do is to run the tests. But for that I need a postgres with encrypthion running handly.
Do you know Yanni?
Cheers
Mariano