> I also had some rather complex piece of SQL from "The Art of SQL", which > took a string and dissected it in place with subqueries and a join to a > pivot table, but wondered if there was an easier way to do it?
If you already have that information in an array in your application code, it might be simpler to create a temporary table, populate it with your entries, and then join on it in your main query, rather than using SQL code to pivot it. Creating a separate table, either using SQL or application code, and populating it with the search items, is really the only way to do what you are wanting to do besides the dynamic generation of the entire query, which has it's own drawbacks, security and performance among them. Brad _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
