Re: optimization/indexing
Re: optimization/indexing
- Subject: Re: optimization/indexing
- From: Chuck Hill <email@hidden>
- Date: Tue, 16 Dec 2008 19:13:41 -0800
On Dec 16, 2008, at 6:23 PM, Guido Neitzer wrote:
On 16.12.2008, at 17:56, Jeff Schmitz wrote:
Hello,
I've populated my eo tables with data and my queries are VERY
slow. A table with about 7000 entries takes a couple minutes to
retrieve a single EO (i.e. row of data). I guessing I need to tell
the database (frontbase) that it needs to index on the attributes
(columns) that I commonly query on. I was wondering, what is the
usual way to do this? Can this be done from EOModeler? I know
this is probably a very basic (i.e. dumb) question.
1. You can do it in FrontBase manager.
2. If you use Wonder and migrations you can use
table.addIndex(columnName)
where table is an ERXMigrationTable and columnName the name of the
column (not the name of the attribute).
3. I think there is a way of defining indexes in Entity Modeler, but
I never used that.
There is. I tried to use it once. It is not quite cooked yet. I
don't recall if it just needed plugin support or if the EOF part
itself needed a few more bits. It will be very nice once this is all
working.
I recently, er, migrated to Migrations. They are quite nice. Before
that I used an SQL script.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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