Re: Problem upgrading to 10.5.3: column named xml

On 29/01/2010 18:11, Rick Hillegas wrote: John English wrote: I've tried surrounding the name XML in double quotes (xml) but that doesn't work. Hi John, Have you tried uppercasing as well as doublequoting the column name. E.g., XML rather than xml? That is *exactly* the solution. I always

Problem upgrading to 10.5.3: column named xml

I am trying to upgrade an old app (v8 or 9) to 10.5.3 but have run up against a serious problem. The DB contains several tables with columns called XML, which is now a reserved word in v10.x. These cause SQL exceptions when the app tries to access them. The older version of Derby that the app

Problem upgrading to 10.5.3: column named XML

I am trying to upgrade an old app (v8 or 9) to 10.5.3 but have run up against a serious problem. The DB contains several tables with columns called XML, which is now a reserved word in v10.x. These cause SQL exceptions when the app tries to access them. The older version of Derby that the app

Re: Problem upgrading to 10.5.3: column named XML

I've tried surrounding the name XML in double quotes (XML) but that doesn't work. It should work. I've used quoting in Derby in similar circumstances quite successfully. Can you post more details about the exact statement you issued and the exact error you received? Note that if you enclose

Re: Problem upgrading to 10.5.3: column named xml

Hi John, Have you tried uppercasing as well as doublequoting the column name. E.g., XML rather than xml? Thanks, -Rick John English wrote: I am trying to upgrade an old app (v8 or 9) to 10.5.3 but have run up against a serious problem. The DB contains several tables with columns called XML,