Issue 575: interface QueryEvaluator { (query) Source: (, ) Nature: Uncategorized Issue Severity: Minor Summary: 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?? Resolution: Revised Text: Actions taken: May 20, 1997: received issue Discussion: End of Annotations:===== Return-Path: Date: Tue, 20 May 1997 07:37:38 -0400 From: Richard Mark Soley To: juergen Subject: [msample@opentext.com: CosCollection vs. CosQueryCollection] Reply-to: soley@omg.org Errors-to: soley_errors@omg.org Issue for the Query Service: ------- Start of forwarded message ------- Return-Path: Date: Mon, 19 May 1997 18:38:34 -0700 From: Mike Sample MIME-Version: 1.0 To: query@omg.org CC: msample@opentext.com Subject: CosCollection vs. CosQueryCollection Content-Type: text/plain; charset=us-ascii Content-Length: 804 Hi all, As I recall, the CORBA 2.0 OQS document mentions that the CosQueryCollection interfaces are temporary until CosCollection is done. Now that CosCollection (ftp://ftp.omg.org/pub/docs/orbos/96-07-09.ps) appears to be done & accepted, will the next version of the OQS formally reference the CosCollection service directly instead of CosQueryCollection (as per the remarks in the appendix of CosCollection)? Or will glue object implementations between the CosQueryCollection interfaces and the CosCollection interfaces need to be provided by the implementor? BTW, in CosCollections it looks like the following interfaces need to inherit from CollectionFactory but do not: BagFactory KeySortedSetFactory SortedBagFactory (according to pg 74 of the spec) Cheers, Mike Sample ------- End of forwarded message -------