Generally speaking, I think that trying to store an unknown number of distinct values in one record column is a bad idea, and it violates level 1 normalization. You really should use a separate table for the phone numbers and/or addresses, one record per instance.
However, I don't mind extensions to the current functionality as long as they conform to the SQL standard. If you look at the SQL-99 standard, on which the ANSI and ISO ones are identical, they include support for user-defined data types. So if SQLite is going to implement them, it should conform to standard. In regards to joins returning duplicate data in multiple columns from one table, the solution to this is simple: do two selects. One select gets one copy of the non-multi-instance data from the master table, and the second gets the multiple-instance data like phone numbers and addresses. Just because you are doing a join, you don't have to return every column the join can see. -- Darren Duncan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
