Unwanted change to queries

Question

We have a view with the following query:
SELECT purord903.ORDERS_ID,
purord903.ORDER_NUMBER,
purord903.COMPANIES_ID_1,
purord903.USERS_ID,
purord903.COMPANIES_ID_2,
purord903.CURRENCIES_ID_1,
purord903.COUNTRIES_ID,
purord903.ADDITIONAL_COSTS,
purord903.CURRENCIES_ID_2,
purord903.PURCHASER_RECEIVED,
purord903.CANCEL_DATE,
purord903.SHIPMENT_DATE,
purord903.EXPECTED_ARRIVAL_DATE,
purord903.SETTLEMENT_TERMS_ID,
purord903.TRANSPORT_TERMS_ID,
purord903.PAYMENT_TERMS_ID,
purord903.DELIVERY_TERMS_ID,
purord903.ORDER_DESCRIPTIONS_ID_1,
purord903.ORDER_DESCRIPTIONS_ID_2,
purord903.ORDER_DESCRIPTIONS_ID_3,
purord903.EQS,
purord903.GSP,
purord903.READY_TO_DISTRIBUTE,
purord903.DISTRIBUTED,
purord903.COMPLETED,
purord903.DELETED,
purord903.RE_SUP,
purord903.CREATED_BY,
purord903.CREATED_DATE,
purord903.CHANGED_BY,
purord903.CHANGED_DATE,
purord903.CAMPAIGN,
purord903.DELIVERY_MONTH,
purord903.DEPARTMENTS_ID,
purord903.COLLECTIONS_ID,
purord903.ROWID FROM PURCHASE.V_PURCHASE_ORDERS purord903
WHERE (purord903.DEPARTMENTS_ID= 55)
But when we do an executequery the query is changed to the following:
SELECT count(1) FROM (***same as above***)
And that results in an error.
Why is the count(1) added to my query?
Best regards
Peter Skriver

Answer 1

Peter:
But when we do an executequery the query is changed to the following:
SELECT count(1) FROM (***same as above***)
And that results in an error.
Why is the count(1) added to my query?SELECT COUNT(1) is for trying to figure out an estimated count of rows (not for actual retrieval of rows--for that we issue another query).
What specific error do you get? Can you post the entire stack trace?
Thanks.
Sung Hi Sung
In the meantime we solved the error, now we are just currious to WHY it added the count function??????????????
Regards
Jeppe Jensen