Tomorrow I may describe two real-world cases where logical uniqueness constraints are difficult or extremely difficult to enforce naturally using standard SQL uniqueness constraints. Both are or can be generalizations of the id,attr,val model, one of them using a timeseries approach to permit point-in-time queries and in-the-future updates. Once more these are cop-outs in that uniqueness on some level is desired, just not the SQL level, but since that's what we're talking about... they seem like fair examples. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
- [sqlite] Why must WITHOUT ROWID tables have P... Nico Williams
- Re: [sqlite] Why must WITHOUT ROWID tabl... Nico Williams
- Re: [sqlite] Why must WITHOUT ROWID ... Nico Williams
- Re: [sqlite] Why must WITHOUT ROWID tabl... RSmith
- Re: [sqlite] Why must WITHOUT ROWID ... Nico Williams
- Re: [sqlite] Why must WITHOUT RO... Nico Williams
- Re: [sqlite] Why must WITHOUT RO... RSmith
- Re: [sqlite] Why must WITHOU... Nico Williams
- Re: [sqlite] Why must W... RSmith
- Re: [sqlite] Why mu... Nico Williams
- Re: [sqlite] Why must WITHOUT ROWID tabl... Richard Hipp
- Re: [sqlite] Why must WITHOUT ROWID ... Eleytherios Stamatogiannakis
- Re: [sqlite] Why must WITHOUT RO... Drake Wilson
- Re: [sqlite] Why must WITHOU... Elefterios Stamatogiannakis