Since table and column names are, respectively, node type and property names, they will in many cases contain a namespace-delimiting colon character. In content repository SQL the colon is therefore considered a valid character within table and column names and does not indicate a parameter, as it would in standard SQL.