-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You might be able to set properties to stop after compiling a query and get its plan. (without executing the query) Take a look at GenericStatement.java in org.apache.derby.impl.sql package...
Satheesh Sandeep A([EMAIL PROTECTED]) wrote: > > >>What sort of input does PLASTIC expect to describe a query plan? > > >PLASTIC takes only the query and shows the plan diagram >All previous implementations of PLASTIC has exploited the facility in >DB2, ORACLE , SQL Server in which the plan is stored in either tables or >it will be returned to the user as ResultSet. In contrast to this in >derby, it won't stores the plan in tables. Moreover we will get the plan >info only after executing the query. This is the major issue which we are >looking for now. > >regards >sandeep > > > > > >On Tue, 5 Oct 2004, Daniel John Debrunner wrote: > > It would be best to discuss this on the Derby developer list. > > What sort of input does PLASTIC expect to describe a query plan? > > Dan. > > > Sandeep A([EMAIL PROTECTED]) wrote: > > >hello dan, > >Iam doing a miniproject as a part of my course to implement PLASTIC in > >derby first outside the engine then to inside the engine. > >PLASTIC is a recent approach to avoid optimization through query > >clustering. > >It has facilities to view plan diagrams in DB2,ORACLE and SQL SERVER. we > >should add the same facility for derby connections also. > >We are looking to modify the code to do as such. > >Any suggestions?? > > >regards > >Sandeep > > > >A.Sandeep > >http://people.csa.iisc.ernet.in/~asandeep > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBYt0PENVNIY6DZ7ERAs5OAJ9DGaalZAS2sU6DRjVBm01D8GCf8ACdFrXt mLhBX2f5Ei0fZSqxkSCkXNE= =uCeu -----END PGP SIGNATURE-----
