Without knowing what you're doing with the data or what your asbtract structure is many will asssume that too many columns means not enough "normalization" of your database.
It's not SQLite -- it's standard database design. http://en.wikipedia.org/wiki/Database_normalization You may be perfectly justified in what you're doing but without explaining what you're doing it raises suspiscions when lots of columns are used. It's usually a bad idea for long-term design and maintenance purposes. Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems ________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Alexey Pechnikov [pechni...@mobigroup.ru] Sent: Saturday, January 28, 2012 9:31 AM To: General Discussion of SQLite Database Subject: EXT :Re: [sqlite] [sqlite 3.6.22] database ".dump" function cannot export table of large number of columns < 2000 2012/1/28 Simon Slavin <slav...@bigfraud.org>: > If this database is for longterm use, you're doing the wrong thing. Those > should be different rows, not all one huge long row. If it's a one-off hack, > then do it and get rid of it before anyone else sees it and shames you. Why not? Please send link to SQLite documentation instead of any astral reasons. -- Best regards, Alexey Pechnikov. http://pechnikov.tel/ _______________________________________________ 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
