Ralph if you want I can write a patch, i'm almost done with it, but time for bed now.

Posted by Maghiel Dijksman (maghiel) on 2010-02-09T19:10:19.000+0000

Here's a patch. Passes all current unit tests.

UNSIGNED_TYPE might not be the best name for the constant,
as this patch only implements integers as unsigned types. But would extending it
to other datatypes be necessary? Maybe for consequence and completeness sake...

Am I taking the right actions to take on bugs like this?
If not, someone please slap me ;)

If this is the right way and this patch is ok, I'll write tests for it tomorrow!
Let me know :)

Posted by Maghiel Dijksman (maghiel) on 2010-02-09T19:26:34.000+0000

I looked at the activity log and it didn't really look like anyone was working on this? So I took the liberty of assigning it to myself. Someone please review!

Posted by Maghiel Dijksman (maghiel) on 2010-02-14T19:07:26.000+0000

Tests

Posted by Maghiel Dijksman (maghiel) on 2010-02-14T19:08:47.000+0000

Please review

Posted by Holger Schletz (hschletz) on 2010-02-25T00:32:16.000+0000

Unsigned integers are not part of the SQL standard and not available on all DBMS. How will this patch affect compatibility with DBMS that don't support it, like PostgreSQL? Is it wise to implement it in their respective adapters?

The constant Zend_Db::UNSIGNED_TYPE is very confusing because UNSIGNED is an additional flag of 'all' numeric data types.
I think it would better to throw an exception if the value to quote has non numeric characters or how do you quote $db->quote('abc', Zend_Db::INT_TYPE);