MySQL Forums
Forum List  »  Falcon

Re: Any plans on supporting FULL-TEXT index, per-table tablespaces and partitioning?
Posted by: Jim Starkey
Date: February 08, 2007 03:37AM

The plan for tablespaces is to have a single, default, per-server tablespace with an option for explicit named tablespaces. This would allow you to define per-table tablespaces. That said, I strongly encourage you not to do this as multiple tablespaces mean a number of independent caches (each has separate page and record caches) which is a difficult or impossible scheme to manage effectively. Why do you want per-table tablespaces?

Full-text search hasn't been resolved. While Falcon has always had full text search, the Falcon and MySQL ideas of what full search means is radically different. Falcon text search is multi-column / multi-table intended to support and web-style presentation of abstract by score while the current server concept is considerably more restrictive. We plan to reconcile the differences, but when or how hasn't been determined (I will probably lose this one and be forced kicking and screaming to the current [adjectives omitted] model).

Falcon will, of course, support partitioning. If there's a problem, please submit a bug report.

Options: ReplyQuote

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.