Issues for Query Working Group of the CORBAservices RTF

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 3: QueryCollection::Collection -- membership scoping
Issue 4: QueryCollection::Collection -- Adding multiple elements
Issue 5: Query Collection::Collection -- Sharing State
Issue 6: QueryCollection::Collection -- finding index
Issue 7: QueryCollection::Collection -- Iterator Position Invalid
Issue 8: QueryCollection::Collection -- iterator updating
Issue 9: QueryCollection::Collection -- destroy methods
Issue 10: QueryCollection::Collection -- reset() exceptions
Issue 11: QueryCollection::Collection -- next_n()
Issue 12: QueryCollection::Collection -- keyed collections
Issue 13: Questions on CosQuery::QueryableCollection interfaces
Issue 69: Updating information via query iterators
Issue 78: How do iterators handle changing of the data they are pointing at
Issue 79: Clarification request for section 11.1.5
Issue 80: Definition of NULL in datafiles without NULL as a concept
Issue 81: retrieve_element
Issue 82: Delegating iterator functionality to the RDBMS
Issue 83: Query language for operations
Issue 84: OQS relation to POS
Issue 575: interface QueryEvaluator {

Issue 3: QueryCollection::Collection -- membership scoping (query)

Summary: I assume that we are allowed to scope membership in a collection via an interface test (e.g, must be rooted off of Collection) and throw an InvalidElement exception?

Summary: Using collection factories, can you add multiple elements at once, and/or add new create methods?

Summary: How do IteratorObjs and CollectionObjs share state?

Summary: On CollectionObj->remove_element_at(IteratorRef), how does the collection "know" the index?

Summary: What does the IteratorPositionInvalid exception mean? Is it only that the user has cycled through the list elements and that no reset() has been issued?

Summary: How does the Iterator know to become invalid when the Collection is altered?

Summary: Where are the destroy methods on the Iterator or on the Collection?

Summary: Can an iterator "reset()" throw an exception such as IteratorPositionInvalid if it is wrapping a db cursor which has no facility for reset?

Summary: Can an interator have a next_n()? Or is this supposed to be via subtyping the interface?

Summary: Is it correct to offer the vanilla collection methods and add a new set for keyed access?

Summary: Clarifications on interfaces which support QueryableCollection.

Summary: When using iterator operations like adding, inserting, etc., how are changes reflected back to the datastores?

Summary: Is it not possible that objects in a collection could have changed in between calls to the iterator accessing them?

Summary: Several of the bullets in section 11.1.5 are unclear.

Summary: Section 11.4.2 para. 3 says that FieldValues may be NULL. What if my datastore is a flat file without a concept of NULL. Does NULL take on the value of empty string for flat files?

Summary: How does this operation work?

Summary: Is there a way that I can delegate the functionality of the Iterators to the RDBMS itself?

Summary: Need all operations on the Collection be made using the SQL-92/QOL-93? If so, how is it possible to handle flat file datastores?

Summary: Need the OQS have any interface with the POS? I don"t see how the two can be interfaced.

Summary: I understand the params to be name value pairs of columns and the values for the
 selection, update, delete, insert criteria
 what is in the query?  I would think if this is the whole query why would you 
 need the params??