Subject | Changing OrderingItems results in unprepare |
---|---|
Author | Geoff Worboys |
Post date | 2016-04-04T04:13:56Z |
Hi Jason,
Some time in the last twelve months (yes, it's been a while
since I updated), you altered TIB_Statement.OnSQLChange so
that the call to SysSQLChanged was moved after the unprepare
is done.
The result is that assignments to OrderingItems (and a few
other properties as well) will always result in an unprepare.
Indeed the change means that parsing UnprepareSQL variable to
the SysSQLChange procedure is pointless, because it is too late
to stop the unprepare from happening.
Do you remember why this change was needed? I'd like to go
back to the way it was, but don't know what I would break.
--
Geoff Worboys
Telesis Computing Pty Ltd
Some time in the last twelve months (yes, it's been a while
since I updated), you altered TIB_Statement.OnSQLChange so
that the call to SysSQLChanged was moved after the unprepare
is done.
The result is that assignments to OrderingItems (and a few
other properties as well) will always result in an unprepare.
Indeed the change means that parsing UnprepareSQL variable to
the SysSQLChange procedure is pointless, because it is too late
to stop the unprepare from happening.
Do you remember why this change was needed? I'd like to go
back to the way it was, but don't know what I would break.
--
Geoff Worboys
Telesis Computing Pty Ltd