Don't get carried away with keys, triggers and stuff like that at this point.
For a start off your example is not normalised. You would have a person table and a food table but then you will need a person-food table as the relationship between person and food is many-to-many so you have to break that up using an 'intersection entity'. Think what you want to store (if anything) in a row like <John, Apple> - it could be things like last-eaten. Then if you think on, you probably will want to break it up again as you will want to hold 'dishes', like peaches-and-cream or eggs-benedict. Work with the data first before getting hung up a SQLite table declarations. -- View this message in context: http://www.nabble.com/normalization-example%28s%29-tp25630323p25648562.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
