Thank you again Igor. By run-time defined fields I meant column names that SQL would not recognise until the query was executed, and therefore are only defined when the statement is "run". I am aware that this is probably not the correct terminology.
Ed Igor Tandetnik wrote: > Ed Hawke > <edward.ha...@hawkeyeinnovations.co.uk> wrote: > >> Out of interest, would I be able to use binding on the run-time >> defined fields? >> > > What's "run-time defined fields"? I'm not familiar with the term. > > >> If I wanted to use: >> >> select * from A >> join B b1 on (A.Column3 = b1.ID) >> join C c1 on (b1.Column1 = c1.ID) >> join D d1 on (b1.Column2 = d1.ID) >> >> join B b2 on (A.Column4 = b2.ID) >> join C c2 on (b2.Column1 = c2.ID) >> join D d2 on (b2.Column2 = d2.ID); >> where d2.ID = ? >> > > Remove the semicolon before WHERE. Otherwise, I don't see anything wrong > with this. > > Igor Tandetnik > > > > _______________________________________________ > 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
