It seems like the more ideal solution would be to create a third table for ownership that contains a person ID and a vehicle ID. This will result in more tables (significantly more if you're trying to migrate object oriented data into a relational model) but is that really a bad thing?
I managed to migrate similar data using this tactic and the biggest issue I've had with it is in the generation of long SQL statements that contain many inner joins (I really wish there was some syntax sugar for automatically joining all foreign keys). This can become tricky if performance is a priority as I found myself needing many unique SQL statements. -Shaun -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of P Kishor Sent: Wednesday, September 09, 2009 1:35 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] how to get "One to many" in 1 row of a table ? On Wed, Sep 9, 2009 at 12:32 PM, Simon Slavin <slav...@hearsay.demon.co.uk> wrote: > > On 9 Sep 2009, at 5:15pm, Stef Mientki wrote: > >> The situation is like this (simplified): >> >> I've a table with persons: name, address, phone, etc. >> I've another table with vehicles: car_or_bike, brand, type, build- >> year, etc. >> The 2 tables are bounded by bind table: person_ID, vehicle_ID > > Well you cannot have one vehicle owned by more than one person. So > you do not need your 'bind' table at all. You just need to add a > column to the vehicle table which contains the person_ID. huh! even though my Saturn is a clunker, it is owned by my wife and I, and until recently, was also owned partially by the credit union via their auto loan... .. -- Puneet Kishor _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users