One rule used in basic systems design is: Define the input, define the output, and the rest will become obvious. If only it were that simple:-) But, a point to ponder.
Fred -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jeff Godfrey Sent: Wednesday, October 01, 2008 9:10 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] seeking storage design assistance Stephen Woodbridge wrote: > It also helps to know how you want to access/manipulate your data and > what you want to do with it in SQL versus with your application. For > instance, you could just store all the cad data as a blob, along with > the attributes in columns. Steve, Hmmm... That's an interesting thought. My initial reaction was "No, I really need direct SQL access to the coordinate data". But, thinking about that a bit more, maybe that's not really true. As you mentioned, I guess I really need to work more on the details of what I want to do with SQL and what I want to do within my application code... Thanks for the input. Jeff _______________________________________________ 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
