Hi! You sql-query must return ALL non-primary-key fields as defined in the repository. If it is a bug or design-choice i don't know although I can guess that it is a design-choice to keep objects complete as far as posible.... Anyone knows??
Example: <class-descriptor class="aClass" table="ATABLE" > <field-descriptor id="1" name="id" column="ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true" /> <field-descriptor id="2" name="anInteger" column="AINTEGER" jdbc-type="INTEGER" /> <field-descriptor id="3" name="aString" column="" jdbc-type="VARCHAR" /> </class-descriptor> Your sql must return anInteger and aString... it is not necesery that it returns id. I guess that it can't demand the primary key if group-functions is used. ----- Original Message ----- From: "Sng Wee Jim" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 28, 2003 5:37 PM Subject: QueryBySQL for ojb rc4 > > Hi, > > > > Anyone encountered problem with using the query type: QueryBySQL? > > > > I am doing something like > > QueryBySQL query1 = QueryFactory.newQuery(java.lang.Class, sql) ; > > Iterator itr = broker.getIteratorByQuery(query1); > > > > however the while iterating through the resultset, the object returned > > by the iterator are all null. > > > > I tried the same query with > > Collection clt = broker.getCollectionByQuery(query1); > > but the size of the return collection is zero. > > > > The resultset of the SQL is not empty. (I ran the SQL in MySQL). > > Is it a bug, or do I need to set some properties? > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]