2013-10-05, 07:26
IMHO empty string ("") should continue to be interpreted as just that, and the item left in the database - there's plenty of examples where fields exist today that are set to the empty string (eg. lastplayed, trailer etc.) which could cause problems if they suddenly started disappearing from the database.
null/None on the other hand is fairly unambiguous, and a suitable trigger for removal.
null/None on the other hand is fairly unambiguous, and a suitable trigger for removal.