Dynamically changing the number of columns included in a D2W query/listing
Dynamically changing the number of columns included in a D2W query/listing
- Subject: Dynamically changing the number of columns included in a D2W query/listing
- From: Daniel Beatty <email@hidden>
- Date: Tue, 21 Dec 2010 22:08:18 -0800
Greetings Gentlemen, Chuck, and Davids,
I am exploring how to limit the number of columns queried and used in for a listing in D2W. My experiment uses ERModernLook, and has a the SDSS DR1 data set. Several of the tables have an annoyingly large number of columns (641 to be precise) and a large number of rows (770k of them). If the JVM is tweaked to 3GB of memory, ERModernLook can return a list from a blank query (taking nearly 2.5GB memory footprint). I have a few more tables with just about as a bad of a scheme and size arrangement. It would be nice to use this data set to measure just how much abuse D2W can handle.
A couple things would be handy for this experiment.
1. How do I use ERDQueryDataSourceDelegateInterface? It appears that the interface requires implementation of the queryDataSource and qualifierFromSender methods.
2. Is there a way to specify different query data sources for different tasks for the same entity (list versus inspect)?
3. How do I get more run time logging from the WO application itself? I thought Shark could do something with the JVM. Can it measure the memory foot print over time? If so, how?
Thank you,
Dan Beatty, M.S. CS (B.S. EECS)
Ph.D. Student
Texas Tech University
email@hidden
http://web.me.com/danielbeatty/My_Home_Page/Welcome.html
(806)438-6620
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden