Preserve nil <-> NULL between Nimrod and database.

[milosn]

This is few simple tweaks to db_mysql that I needed. Not sure you want this kind of behaviour where NULL is converted to nil and nil to NULL ... in my mind thats logical.

[reactormonk]

Why is NULL in SQL different from nil in nimrod?

[milosn]

Thats the wrong question ... I was doing this little ORM project for work in Nimrod and discovered that db_mysql is broken basically ... This patch fixes the breakage and decides that NULL from the database will be represented as nil when db_mysql returns the record set. Also it decides that if nil is passed in for UPDATEs and INSERTs it will insert NULL into the DB. I am just asking if my logic is correct and thats how it should be?

I have higher level code which reads table descriptions and converts string values and nil-s that db_mysql with this patch returns into ints, floats and strings(keep as it is).

[milosn]

Hi guys, is this any closer to getting merged? Just asking because I have nimrod RPM which i am building weekly and this is an extra patch which needs to be maintained.

[dom96]

@Araq What do you think?

[dom96]

@Araq gave the ok on IRC.

But before I merge this I think the changes need to be replicated for the other db* modules. Could you do that? And also add some documentation to dbQuote?

[milosn]

Yes i think so, i have postgres install in some VM someplace ... Ill have a look.