Well if you want to share the db with java people python pickling is out of the question and a list would be problematic since it's not a native sqlite data type. I would suggest the two tables approach as suggested: main->pri_id,name marks->pri_id,mark (400 of these per main)
Also maybe a relational database in this case might be overkill but that depends on if you want to query the data(no query=no database) and how large the data will be(large=db), if it will be updated(db easier), etc. ~G On Thu, May 7, 2009 at 8:18 PM, chandramouli s <[email protected]> wrote: > Yes what I was looking for is a way to store the values(400 fields) in > 400 columns with just an ID column to identify the record. In the > absence of a convenient method to do that (automatically generate 400 > column names) I decided that storing it as a list would be convenient. > Yes pickling also might work, but ideally I would like to generate 400 > columns or store it as a list. I intend to share the data with people > coding in Java but a sqlite db seemed more convenient than a flatfile > (to explore the data or to verify parts of it or correct it). -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
