All I meant was that in a database you have defined tables with defined column names. These are defined before any SQL statements are executed and therefore I would classify them as pre-defined.
Contrast this with the "labels" applied to tables to create a separate reference to them within an SQL statement (e.g. a2 in your example). Before the SQL statement creating these references is executed then they will not be "recognised" by anything (i.e. any references to them in other statements will throw up an error). Therefore these are only defined when the SQL Statement that defines them is run, and therefore I would classify them as run-time defined. I am aware as I said that these are probably not the correct SQL definitions, they were self-applied definitions to help make clear what I was referring to. I can only apologise that it made it more complicated. Ed Igor Tandetnik wrote: > Ed Hawke wrote: > >> By run-time defined fields I meant column names that SQL would not >> recognise until the query was executed >> > > I don't get the distinction. Could you give an example of column names > that SQL would somehow "recognize" before a query is executed? What do > you mean by "recognize" here, anyway? > > 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
