It seems that the TIBQuery is effectivley read-only
when not coupled with a TIBUpdateSQL component.
It would be nice if the TIBQuery did not require a
TIBUpdateSQL component to do edits of a dataset.
The situation:
It is better to use a query component than a TIBTable
when working with remote clients via TClientDataSets.
By requiring the TIBUpdateSQL component to accompany
the query, it nearly doubles the number of components
needed in a given DataModule.
Using the same methods introduced in TIBTable, a
TIBQuery could manage its own updates, inserts,
deletes, etc. This would allow for more targeted use
than a Table (where clauses) while not forcing the
component clutter to increase.
It could be implemented as an option like on the
TQuery. A "RequestLive" like property. It would also
need the UpdateType so it could limit it to the
primary key for locating the record to change.
Logged In: YES
user_id=59511
IBX has taken the approach it will not write your SQL for
you. There are no plans to change that. TIBTable emulates
a table paradigm which is an exception. All components that
work from a developers standpoint at the SQL level do not
autogenerate code on the fly and this probably will not change.