• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: optimization/indexing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: optimization/indexing


  • Subject: Re: optimization/indexing
  • From: Guido Neitzer <email@hidden>
  • Date: Tue, 16 Dec 2008 19:23:11 -0700

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.

cug
_______________________________________________
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


  • Follow-Ups:
    • Re: optimization/indexing
      • From: Chuck Hill <email@hidden>
References: 
 >optimization/indexing (From: Jeff Schmitz <email@hidden>)

  • Prev by Date: optimization/indexing
  • Next by Date: Re: optimization/indexing
  • Previous by thread: optimization/indexing
  • Next by thread: Re: optimization/indexing
  • Index(es):
    • Date
    • Thread