>
> I'd recommend continuing down the path you are exploring which is having
> test data and tweaking/tuning/correcting your queries until they are
> acceptable.
>
> You'll probably find it easier to write the processing algorithm in the
> programming language of your choice. This will allow you to print out
> diagnostics as you go along, play with a debugger etc. To make it easy
> to map back to SQL you should structure it as a for loop over the rows
> of data with inclusion/exclusion conditions at the top of the loop. If
> you decide to express it in SQL again you can then run your correct
> language code against SQL and compare the results as your test
> framework. (Strictly speaking you are already doing this but the
> programming language is your brain :-)
>
Thank you for the advice.... Can you point me to some examples of code in a
traditional language and the equivalent in SQL?
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
