I meant to attach some language that would give me more flexibility than straight sql.
On Wed, May 11, 2011 at 10:35 PM, John <tauru...@gmail.com> wrote: > I've developed a mobile app that I want on all smartpnones (that means at > least 4 different platformorms/languages). I've managed to put 80% of logic > in sqlite db (which is on all smartphones). The idea is that the more I can > put in sqlite the less I have to explain to four different programmer - less > bugs, less time wasted. It's definetelly not the most efficient > implementation this way, but it makes it easier to scale accross platforms. > If I could attach some procedural logic to my db (which would work on all > platforms), I would be very happy. > > On Wed, May 11, 2011 at 10:19 PM, Pavel Ivanov <paiva...@gmail.com> wrote: > >> > I can't trully construct sql statement piece by piece with SQL >> > db as I did with Oracle. Just wanted to confirm. >> >> Why do you need to construct SQL specifically with db's tools? Why >> can't you do that in your host language? >> Oracle needs dynamic SQL feature because it will work much faster than >> the same made in the application which will have to do a lot of >> network round-trips while gathering pieces together. But in SQLite >> there is no such thing as network round trip and so dynamic SQL won't >> work any faster than the same logic in your application. In fact it >> would work even slower because SQLite would have to implement >> something general with lots of different features and you can >> implement something simple and optimized to your particular use case. >> >> >> Pavel >> >> >> On Wed, May 11, 2011 at 10:03 PM, John <tauru...@gmail.com> wrote: >> > Yes, I could. But considering that I'm applying tons of logic and not >> just >> > selected this would be a real mess. Not even sure I could pull it. >> > Normalization was something I lacked with regard to previous post. But >> in >> > this case, I don't think it has anything to do with it. It's just alack >> of >> > dynamic sql. I can't trully construct sql statement piece by piece with >> SQL >> > db as I did with Oracle. Just wanted to confirm. >> > >> > On Wed, May 11, 2011 at 9:58 PM, Nico Williams <n...@cryptonector.com >> >wrote: >> > >> >> On Wed, May 11, 2011 at 8:47 PM, John <tauru...@gmail.com> wrote: >> >> > That would work if I needed to select a single column from a table. >> But >> >> if I >> >> > need to select multiple values (c1, c2), then it wouldn't work. Can't >> >> have >> >> > subquery with more than one column selected, in general, I think. >> >> >> >> You can do one case for each result column. It gets wordy, fast. >> >> >> >> Normalization helps... :) >> >> >> >> Nico >> >> -- >> >> _______________________________________________ >> >> sqlite-users mailing list >> >> sqlite-users@sqlite.org >> >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> >> >> > >> > >> > >> > -- >> > ~John >> > _______________________________________________ >> > 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 >> > > > > -- > ~John > -- ~John _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
