Fine. Do the "a2-style" (for want of a better way of defining them) names exist outside the SQL statement which defines them?
i.e. if I execute the example statement that you gave me, then later execute a statement which references c2 will that work? Will other statements in the same transaction be able to reference c2, or does the reference only persist in the statement in which c2 was defined? Ed Igor Tandetnik wrote: > Ed Hawke wrote: > >> 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 don't see how this fine distinction is interesting, nor why it's worth > making. While "predefined" column names may exist, in some philosophical > sense, outside the context of a SQL statement, the only way for you to > use them or refer to them is by mentioning them in a SQL statement, at > which point all distinction between "predefined" and "dynamically > generated" names evaporates. > > 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
