Interesting you should classify my data need as a waste without knowing anything about my application. What if I want to calculate a percentage that the first column is of the total - would it still be a waste to calculate the total?
As far as I'm concerned , the more data manipulation that can be done by the underlying db system, the better. That way my application is protected from database structure changes. Subject to performance considerations of course. Isn't that one of the purposes of db systems? Pete Haworth On Nov 15, 2009, at 4:00 AM, sqlite-users-requ...@sqlite.org wrote: > Think about what you are asking for... your result set is going to > contain two columns. The first column will have different values for > every row, but the second column will have the same value in every > row. Something like so... > > 5 33 > 3 33 > 7 33 > 4 33 > 9 33 > 5 33 > > and so on. What a waste. Still, if you insist on something like that, > do it in your application. Else, run two separate queries and union > them as Kees showed you. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
