Re: Live Search

On Sun, Nov 29, 2009 at 19:50, Stewart Lord <stewey@ambitious.ca> wrote: > On 28-Nov-09, at 9:36 AM, Hannes Magnusson wrote: > >> On Fri, Nov 27, 2009 at 19:47, Stewart Lord <stewey@ambitious.ca> wrote: >>> >>> I would like to hear what you both think of how this is progressing. Any >>> gotchas? Let me know if you would like to see the search-api.php source. >>> If >>> I am on the right track, I can move on to the front-end. >> >> We like codes, please post a pastebin link :) >> I assume you are focusing on the sqlite database itself, right? >> >> Daniel is working on getting all mirrors to run a relatively >> recent-ish version of PHP (5.1.6 or something, due to fudging CentOS >> mess) with SQLite enabled (any of the.. 4? variants). >> >> When all mirrors have added SQLite I was thinking we should face out >> the filename fallback and only use the sqlite database. >> Furthermore, the database that PhD generates contains a good chunk of >> information and is more accurate then the current sqlite database. The >> database generated by PhD is used by the manual itself so it is 100% >> correct and contains not only IDs (filenames) and reference >> (function/method) information but also reference info (description) >> which would be pretty cool to get in the autocomplete info. >> >> On the otherhand, the currently generated database by PhD doesn't >> contain metaphone() info or such things, but could easily be added.. >> >> -Hannes > > > Hi Hannes, > > Ooops! I wasn't using SQLite. I'll take another run at it this time using > SQLite and report back. FWIW, here is the pastebin link: > > http://pastebin.com/m4eaee92d After line 15 there is a missing exit; There are no guarantees that the webserver has write permission to any directory. But that shouldn't be needed with the sqlite search anyway, right? -Hannes