[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Neil, I think what you describe as a database, people with a formal IT background would consider a database plus a set of applications to simplify access to it. These applications, for instance, take your search form and turn it into queries that can be processed by the database layer. MySQL really is just the database bit -- the data storage engine(s) and a query language to get at the data. People would argue that the processing for a search form, for example, really doesn't belong in a database implementation because ideally it should be possible to create such a form and then switch databases between MySQL, Postgres or Oracle merely by changing the interconnecting logic, without the creator or end-user of the form even being aware of it. Plenty of people find databases perfectly usable without this extra layer of middleware -- there are no end of applications where data is stored and used without any human ever wanting to look at it interactively. As regards finding the functionality you're after, though I use MySQL a good deal I'm afraid I really don't know of anything that suits your needs. James -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html