Subject RE: Re[3]: [IBO] IBO rev 2785 and default values
Author Jason Wharton
Hi Marcin,
Yes, I've been thinking about this and I am actually taking a look at it right now.
What if I did this:

GetServerDefaults would be changed to GetServerDefaultsMode that would have three values.

sdfOnPost (the default)
I will make the sdfOnPost setting have the following behavior:

Dataset goes into insert mode.  No defaults are acquired from the server, yet.  When the record is posted it will determine values that are still null and then plug in a value for them from the server default value, if available.
The other two modes are self-explanatory.
Therefore, for you, the legacy behavior you wanted will still be there and the desirable aspects will also still happen as well.
What do you think?
Jason Wharton

From: []
Sent: Wednesday, October 31, 2018 10:40 AM
Subject: Re[3]: [IBO] IBO rev 2785 and default values


Hi Jason

Is it possible that we can get back to below discussion?
I'd like to know if you're going to modify the way IBO treats defaults
from the server?


------ Wiadomość oryginalna ------
Od: "Marcin Bury" <marcin.bury@...>
Data: 07.08.2018 21:15:20
Temat: Re[2]: [IBO] IBO rev 2785 and default values

>Hello Jason
>First of all - thank you for prompt
>Getting default values from the server is generally
good thing. There
>is nice feature 'Import server defaults' that fills
>Then there is property
GetServerDefaults - which is by deafault ( ) set
>to false.
would like to have control on application side if a query utilises
>server defaults or not. Isn't it the purpose of GetServerDefaults
>For currency fields I always use domain defined as
>default 0. This default is actually to cover my lazy back
in case of
>... In this particular example null value means something
>than 0 value. Quite often I use following scenario: while
adding new
>record such a field is intentionally left blank, if the user
wants to
>put there some explicit value - he is more than welcome - 0 is
one of
>possible explicit values. If while saving the record this field
>still bank, some predefined calculations are performed and their
>is written to this field.
>Then I would get back to
my second case - what was your intention to
>get defaults for
>Jason, I always appreciate and admire your hard work,
simply sometimes
>don't follow you intentions
>------ Wiadomość oryginalna
>Od: "'Jason Wharton' jason@... [IBObjects]"
>Data: 07.08.2018 20:37:09
>Temat: RE:
[IBO] IBO rev 2785 and default values
intent was for these changes to be an improvement. IBO's core
>>philosophy is to have all of the aspects possible from the server be
>>part of things on the client. I want server declared default
>>to be utilized on the client. Perhaps you could explain to me
why you
>>want a NULL default rather than the server declared default.
>>probably just don't understand why this would cause a problem
>>of being
>>Sent: Tuesday, August 07, 2018
1:51 AM
>>Subject: [IBO] IBO
rev 2785 and default values
>>It seems that you modified the way IBO works with
columns' default
>>values. And it also seems that you made a step too
far .
>>If a column is based of domain with default value this default
>>taken when adding new record (previously IBO was
keeping null value),
>>but what is more annoying that IBO sets the
default value for
>>I have a stored procedure
that has and integer parameter based on
>>with 0 as
default value. Procedure is prepared to accept null value in
parameter and 'behave' accordingly. What was my surprise when IBO
0 for this parameter 'without asking'
>>So, could you
reconsider your changes?

[Non-text portions of this message have been removed]