Subject Re: [Firebird-Java] testing RC2: strange GDSException on a query
Author Blas Rodriguez Somoza
Hello Haris

At 13/01/2003 17:39 +0200, you wrote:

>As you can see the table has many columns (90). SELECT * from product works
>with DbVisualizer 3.1 using
>FirebirdSQL RC2. It does not work using my bean though(which uses JBuilder
>API).
>Using my bean, I managed to execute the following query:
>-----------------------------------------------------------
>SELECT prdId, name, retailPrc, retailPrcEU, descr, descrLG,
>prdHasAttributes, img, hdBeginDate, hdEndDate, hdStockFlag, salesFlag,
>stockQua, catId, deliveryDays,
>prdId2, nameUp, nameLG, nameUpLG, supplierId, vatPct, mUnit, mUnitLG,
>wholesalePrc, wholesalePrcEU,
>wholesalePrcCUR1, wholesalePrcCUR2, retailPrcCUR1, retailPrcCUR2,
>slWholesalePrc, slWholesalePrcEU, slWholesalePrcCUR1,
>slWholesalePrcCUR2, slRetailPrc, slRetailPrcEU, slRetailPrcCUR1,
>slRetailPrcCUR2, hdWholesalePrc, hdWholesalePrcEU, hdWholesalePrcCUR1,
>hdWholesalePrcCUR2,
>hdRetailPrc, hdRetailPrcEU, hdRetailPrcCUR1, hdRetailPrcCUR2, giftPrc,
>giftPrcEU, giftPrcCUR1, giftPrcCUR2, weight, cubemeter, minOrderQua,
>maxOrderQua, safetyStockQua, package, packageLG,
>img2, img3, img4, barcode, hdStockFlag, hdStockFlagW, hotdealFlag,
>hotdealFlagW, salesFlagW, hdBeginDateW, hdEndDateW, shippingKindZone,
>shippingValue, shippingValueEU, shippingValueCUR1, shippingValueCUR2,
>shippingVatPct,
>inQua, outQua, inVal, inValEU, inValCUR1, inValCUR2, outVal, outValEU,
>outValCUR1, outValCUR2, prdLock, prdHideFlag FROM product
>----------------------------------------------------------
>
>I left out 7 columns. I tried to add any of the other columns and the same
>exception was thrown.
>I believe the problem has to do with the number of metadata retrieved from
>the database and that sth has also to do with JBuilder API (correct me if
>I'm wrong this is just black box testing).

Thanks, good information, enough to solve the problem.

The problem appears apparently because the engine does not like too much unions or because the statement length.

I have committed into CVS a patch for the problem. Now if there are too much columns, the column information query are splitted into several querys. I have tested with your table and it works.

Regards
Blas Rodriguez Somoza