numeric null fields must be emtpy not null

[Ferdinand]

at least numeric stored function fields with calue Null are reported as 0 - but must be shown as empty.

[Albert Cervera i Areny - http://www.NaN-tic.com (albert-nan)]

A Dijous, 6 d'agost de 2009, Ferdinand @ ChriCar va escriure:
> Public bug reported:
>
> at least numeric stored function fields with calue Null are reported as
> 0 - but must be shown as empty.
>
> ** Affects: openobject-client-kde
> Importance: Undecided
> Status: New

That's not the behaviour of the GTK client, don't know about eTiny. What do
you think we should do?

--
Albert Cervera i Areny
http://www.NaN-tic.com
Mòbil: [phone]

[Ferdinand (office-chricar)]

daily work shows that it's a difference if I have entered 0 or null
null: I have not (yet) entered anything
0 : I have entered zero

so my preference are clear - as the title says

BTW also programs might behave differently depending on null or zero
the way it is now the user can't reproduce the behavior because the difference is not "visible"

[Albert Cervera i Areny - http://www.NaN-tic.com (albert-nan)]

After a second thought. The main problem with this feature, is not the implementation itself, but that I'm sure many modules currently available would crash. Many modules won't have a float field as required but will depend on having a valid value when calculating. That would bring up lots of crashes.

I don't think implementing this in Koo only is a realistic solution. Also, I'm not sure it's even necessary. I've not needed such distinction (between zero and null) in my modules until the moment.

[Ferdinand (office-chricar)]

I thought it's "only" a display issue

I have an application where I have to enter target values
* nothing entered: target = empty
* 0 entered: target = 0

[Ferdinand (office-chricar)]

to be discussed for ALL clients

[Ferdinand (office-chricar)]

Example - want to record temperature in a numeric field

null - no value available
0 - zero degree

currently not possible because 0 and null are displayed as 0