query columns now use the ColumnSettings of the underlying table column, if
- this table column can be determined
- the query column doesn't have own settings (which would overrule the table col settings)
However, we're not there, yet: Changing the settings of the table column is not reflected
in the query column until closing and re-opening the database document. That's up to a next
implementation step.
2007/10/29 22:44:05 fs 1.31.108.2: merging changes from CWS dba24b herein, to not wait for later resync
2007/09/12 09:09:37 fs 1.31.108.1: PROPERTY_(ID_)USE_ESCAPE_PROCESSING: removed the USE_ for consistency reasons
2006/08/01 13:56:39 fs 1.28.8.2: #i10000#
2006/07/21 11:02:13 fs 1.28.8.1: during #i67635#: don't delete m_pColumns in ::disposing, but in the dtor only
2006/07/03 19:48:47 fs 1.26.78.6: #i51143# warning when trying to obtain columns for a query whose statement does not produce a result set
2006/06/30 13:27:18 fs 1.26.78.5: #i51143# protect against recusive sub queries
2006/06/28 10:31:07 fs 1.26.78.4: #i10000#
2006/06/27 11:58:02 fs 1.26.78.3: RESYNC: (1.26-1.27); FILE MERGED
2006/06/16 11:47:37 fs 1.26.78.2: during #i51143#:
refactored VCollection:
- createEmptyObject now named createDescriptor
- cloneObject removed
- appendObject now returns the newly created object
(previously done via a subsequent call to cloneObject)
2006/06/01 12:32:55 fs 1.26.78.1: #i51143# also try to retrieve columns if the EscapeProcessing is FALSE - may be we're lucky ... (needed when such a query is added to the query designer)
