On 6 Apr 2010, at 5:50pm, BareFeet wrote:
> If the logic is built into the SQL itself, then the other development
> language is not an issue. I can open my SQLite database files in a GUI tool
> written in Objective-C or the command line tool written in C, or a PHP front
> end to a web page, etc.
In SQLite there's a certain amount of logic which can be carried out or
enforced by TRIGGERs and FOREIGN KEYs. I can imagine a competent hacker
setting up a database with a lot of these and using the resulting database
without any other programming language support, possibly even from the sqlite3
command-line tool. If you add a SQLite GUI database manager to that you might
even have a usable environment for someone who is fairly techie but not a
programmer.
So I just spent a couple of minutes imagining what that would be like. I think
it still won't result in anything a non-techie can use. Error messages from
FOREIGN KEY constraints, for sure, wouldn't be much of an explanation to a
non-techie user as to what they did wrong. ("No you can't save this list of
ingredients because I don't know what 'linguini' is.")
So you'd have to do the whole thing with TRIGGERs, because they can have
specified error text. Which is not normal (mostly constraints are imposed by
the programming around the SQL logic, done in whatever programming language the
programmer uses). Which means you'll want schema specially designed for your
GUI environment. Which is why you won't be using any existing SQLite template
files.
Simon.
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
