Page 1 of 1

[Solved] Can NOT use a Number naming View anymore

PostPosted: Mon Jan 25, 2021 4:09 am
by dreamquartz
Hello All,

I use Views in my DataBase and used to be able to name a view something like vABC23.
I now have to create new views so I do not know since whene I can not do this any more.

Does anyone have this same issue?

Dream

Re: Can NOT use a Number naming View anymore

PostPosted: Sat Feb 27, 2021 8:04 pm
by dreamquartz
dreamquartz wrote:Hello All,

I use Views in my DataBase and used to be able to name a view something like vABC23.
I now have to create new views so I do not know since whene I can not do this any more.

Does anyone have this same issue?

Dream


My process: I create a Query e.g. qABC123, and then create a View called vABC123 from it. I use this naming convention to be able to trace back where a View comes from.

After much research, I determined that if the DataBase is NON-split (ergo the internal DataBase coming with LO), a View can be named as: vABC123.
I use a split situation using HSQLDB 2.5.1. Here you cannot create a view directly from a Query that in itself holds numbers in its name.
I have to rename it it in Direct SQL.

Dream