This topic is locked

Add "set NULL if empty" option

10/25/2010 6:00:09 AM
Suggestions
J
jevobz author

Hello there,

I'm newbie user of PHP Runner (version 5.2), I'm mostly MS Access forms developer.
One strange thing I found, is that there's no obvious way to write Null values to the database, PHP Runner generates empty strings instead. My MySQL database structure relies heavily on Unique indices, where Null column is used - it allows me to have unique filled values. In case of empty strings, such technique cannot be used anymore.
So I recommend to add option to field properties: "set NULL if empty". I think this problem is too general to ignore or try to solve with event-based hacks.

O
OLDmrcaseyman 1/21/2011



Hello there,

I'm newbie user of PHP Runner (version 5.2), I'm mostly MS Access forms developer.
One strange thing I found, is that there's no obvious way to write Null values to the database, PHP Runner generates empty strings instead. My MySQL database structure relies heavily on Unique indices, where Null column is used - it allows me to have unique filled values. In case of empty strings, such technique cannot be used anymore.
So I recommend to add option to field properties: "set NULL if empty". I think this problem is too general to ignore or try to solve with event-based hacks.



I would like to ask for this feature also.

S
surfermac 1/21/2011

I third that

R
rkiss 3/8/2011



I third that


Same Here.

Sergey Kornilov admin 3/10/2011

Thank, guys, added to the list.

A
asawyer13DevClub member 12/30/2011



Thank, guys, added to the list.


Sergey,

Is this still an issue with PHPR 6.0?
Alan

G
georgetetterton 1/7/2014

Has this been fixed yet?

L
lewis 7/2/2014

This is a very important feature for us as well since empty strings cause problems with constraints, analysis, and reports. Is there any update for this idea? Is there any chance PHPRunner 8 might have such an option? With 15,000 views it seems there is significant interest.
Thanks.

A
asawyer13DevClub member 12/16/2015

Did this get corrected in v8.1?