I suppose I should have stated my goal even further. I'm putting them in sql so that I can query it row by row (i.e. operationId by operationId), as opposed to SELECT all operationIds, then foreach operation id select all rows where operationid = ...
On Thu, Dec 5, 2013 at 1:44 PM, Igor Tandetnik <i...@tandetnik.org> wrote: > On 12/5/2013 4:31 PM, Hayden Livingston wrote: > >> --> End Goal: >> >> A SQL Table: >> >> FooId,SomeStringValue,SomeIntValue,SomeOtherColumn, >> WhateverColumnNameItNeedsTo, >> > > You do not want a table with an open-ended set of columns - SQL doesn't > work that way. You want a fixed schema; let the number of rows be > open-ended. Something like this: > > ComponentId, OperationId, ColumnName, Value > > See also http://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2% > 80%93value_model > -- > Igor Tandetnik > > > _______________________________________________ > 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
