DefaultFields and CachedUpdates
- Thread starter nicofari
- Start date
Not that I know. What exactly goes wrong?
I have a table with some date columns not null with
default '1/1/3000'.
There is a view built after this table.
An OracleDataset is attached to this view,
with CachedUpdates=True and DefaultFields=True.
When we try to post a new record without compiling one of these fields, the default is
not applied (happens an error "the field xx must
have a value)
There is also a OnNewRecord event defined on the OracleDataset. In this event these fields are NOT
compiled.
The editing form contains a grid.
Now I forced the default in the OnNewRecord event
replicating the database's ones...
default '1/1/3000'.
There is a view built after this table.
An OracleDataset is attached to this view,
with CachedUpdates=True and DefaultFields=True.
When we try to post a new record without compiling one of these fields, the default is
not applied (happens an error "the field xx must
have a value)
There is also a OnNewRecord event defined on the OracleDataset. In this event these fields are NOT
compiled.
The editing form contains a grid.
Now I forced the default in the OnNewRecord event
replicating the database's ones...
The TOracleDataSet does not see the default values of the underlying tables of a view. You will have to set them manually. This is a restriction of views, not cached updates.
Similar threads
- Discussion
