I almost raised an issue for this, but then I started thinking it was odd that no-one else had ever mentioned it, so I thought maybe it was better to ask via email first...
As far as I can tell, Empire DB will refuse to write an empty string to a column if it is "NOT NULL". This is true for any database type since the logic based on a call to ObjectUtils - it's not the responsibility of a particular engine's driver (in my particular case the error is coming from DbRowSet line 680 as I add a new row). Now I know that Oracle, and perhaps some other databases, store empty strings as nulls. But not all databases do so! I am pretty sure that HSQLDB does not, for example, since 1.7.2 - see http://hsqldb.org/doc/guide/ch06.html#N10F73 And I am also pretty sure that SQL standards make a distinction. So could this be fixed? Alternatively, if it's a known issue that has a reason, is it documented somewhere? Or if I've messed up, and this *does* work, please say so I can fix my bug... (I'm not really sure why Empire DB is checking this at all. Isn't this the database's job?) Thanks, Andrew
