Jim Starkey suggests that one could alter the semantics of the special case DELETE FROM TABLE (with no row restriction clause) to accomplish the same thing.GSplit permits you to easily break your large files down into smaller, more manageable pieces. PURGE could be called from stored procedures but the COMMIT to execute it would have to be executed from the application since stored procedures can't commit. would cause no deferred garbage collection.would run orders of magnitude faster than a DELETE.would return all data pages and index pages to the free list.would require exclusive access to the table.would require no (or active) DELETE triggers on the table.would require no foreign key dependencies by other tables on it.would be a deferred operation that doesn't happen until COMMIT.PURGE would behave similar to DROP table except that it would preserve all table-related metadata. Charlie Caro proposes implementing a new statement, PURGE, as exists in some other database products. It's so common for users to delete all rows in a table, that we should consider adding a special command to optimize this operation. Add SQL security to GRANT certain users or roles the privilege to receive notification of an event class.Allow events within or outside a transaction.Permit multiple asynchronous event handlers for any given event.one event handler for event FOO, a different event handler for event FOO.BAR, and a different event handler for event LIME. Permit different asynchronous event handlers for different event classes, i.e.Deferred events so a client could log on and get a sequence of events that have been queuing up.Create an "event cursor" mechanism so the client could retrieve the event name/class, info about the event (who posted it, for example), the number of arguments, and the data of the arguments themselves.Make sure there are components for Delphi/C++Builder/JBuilder that take advantage of the new Event technology.with the regular expression /^FOO$/, but also match with the regular expression /^FOO.*/. In other words, instead of matching an event based simply on exact string, the event matching algorithm would match based on exact string, i.e.
These statements would all receive the event posted in the example above. For example:Īllow clients to listen for classes of events. Implement hierarchical events and allow data arguments to be passed with an event. We should make a quantum leap in event technology, to provide a new paradigm in "push" technology.
0 kommentar(er)
