In my scenario, I personally changed (in plain sql) the 'shipped' field to NULL for id=1. But it could happens that in a "natural" database (without using direct sql queries), some boolean fields can have these 3 values. I've checked in some of my databases and this is the case, some boolean fields are 'true', 'false' or NULL'. So we need to do something about the fact that a boolean field could eventually have 3 different values in one database. We could: * consider None values as False * group by: false, true and undefined (for NULL values)
Since the server is sending 'False' for NULL values, we cannot use the second solution, so we'll need to group by: * True: for 'true' values * False: for 'false' and NULL values So we need to display 2 lines (not 3). Personally, I find this ternary logic stupid but since the SQL standard has been defined like this, we have no choice and we need to have a lot of specific code to handle this case. Hope this helps. -- https://code.launchpad.net/~openerp-dev/openobject-client-web/6.0-opw-18489-msh/+merge/80893 Your team OpenERP R&D Team is subscribed to branch lp:~openerp-dev/openobject-client-web/6.0-opw-18489-msh. _______________________________________________ Mailing list: https://launchpad.net/~openerp-dev-gtk Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-dev-gtk More help : https://help.launchpad.net/ListHelp
