[wp-trac] [WordPress Trac] #15158: wpdb insert & update with null values
WordPress Trac
noreply at wordpress.org
Fri Jan 4 18:56:00 UTC 2013
#15158: wpdb insert & update with null values
-------------------------+-----------------------------
Reporter: westi | Owner: sorich87
Type: enhancement | Status: accepted
Priority: normal | Milestone: Future Release
Component: Database | Version: 3.0.1
Severity: normal | Resolution:
Keywords: has-patch |
-------------------------+-----------------------------
Comment (by deltafactory):
Replying to [comment:29 jbutkus]:
> I think that (`$wpdb->enable_nulls = true;`) would introduce more
trouble, than anything else. As somebody would set it, and then forget to
reset, while others would expect it to be in one position.
Of course, you're right. My general idea was this: At this point,
developers should be required to intentionally choose to use nulls since
every bit of code out there was written with the understanding that a null
couldn't be inserted. As you help point out, if it's dangerous to enable
it within a single page load, it would be disastrous to make the global
default.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/15158#comment:30>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list