Mike,
What a brilliant idea! Seriously, setting up a community fund to sponsor this (and perhaps in future other things) might be something to consider.
The only questions that come to mind are:
1. Which would be more effective, setting up a fund for this sort of thing or just going out and buying licences for MySQL/InnoDB and/or InnoDB hot backup?
I think you're on the right track. MySQL & Innodb could add a check box on their order form that says something like
"Please donate $50 towards the InnoDb FullText search project". (MySQL AB can use any dollar amount that they're comfortable with. I only used $50 as an example)
This will help MySQL AB get more licenses and InnoDb could sell more Hot Backups.
When the donations reach a specific level, InnoDb starts work on the FullText search feature.
2. What sort of amount would be required to sponsor it?
Only Heikki can answer that. It is definitely a feature that is long overdue.
If people like me are staying with MyISAM tables because InnoDb lacks FullText support, then it's also impacting InnoDb's Hot Backup sales. So it is in their own best interest to get started on the project. :)
Mike
On Fri, 2003-09-05 at 14:36, mos wrote:
> At 08:56 PM 9/4/2003, you wrote:
> >Hi all,
> >
> >At the moment, we all know that InnoDB does not yet have FULLTEXT
> >indexes. This is not another message asking as to when we will have that
> >functionality.
> >
> >This message is different. On the mailing list for DBMail, we've been
> >discussing MySQL table types, with everyone highlighting the fact that
> >MyISAM does not support transactions while InnoDB does (in addition to
> >foreign keys). Then, I raised the point that MyISAM may not have
> >transactions, but it does have FULLTEXT indexes, which could be a
> >massive source of speed for MyISAM-based tables.
> >
> >My question is this: Obviously, if you throw SQL statements enclosed in
> >BEGIN/COMMIT and issue ROLLBACK statements on MyISAM tables, MyISAM does
> >the right thing and ignores it (personally, I think it would be better
> >if it alerted the nearest admin, so that they could come and deal with
> >any person touching their finely tuned database server).
> >
> >Is the converse-ish statement true? Is there any way that FULLTEXT
> >searches could be executed on InnoDB (and other type) tables currently
> >or with a quick patch that uses a full table scan? I'd be willing to get
> >together with a few people to write such a thing, as it would speed
> >development while FULLTEXT is a MyISAM exclusive while still allowing
> >testing against all MySQL tables in the immediate future.
> >
> >Regards,
> >
> >Chris
>
> Chris,
> I agree with you, FullText in InnoDb would be nice. It is one
> reason why I'm sticking with MyISAM tables. I suppose you could modify
> MySQL to implement FullText on InnoDb tables but then who would support it?
> It would be a variant of MySQL. It would be better if InnoDb implements it
> so they would support it in all future MySQL versions.
>
> Heikki did mention a year ago that he would consider implementing
> FullText searching if a client was willing to fund it. Unfortunately he
> didn't say how much $ it would take. I would be willing to kick in $100 to
> see it happen. If enough people got together, perhaps we can encourage him
> to do it. I suspect not having FullText in InnoDb is a major hurdle that
> is forcing people to stay with MyISAM tables.
>
> Mike
>
>
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
