I updated EDB from 2.13 to 2.17 and got an error of unvalid column
definitions.
In a kind of  crosstable I used "_22.2.201" as a column name e.g.

That doesn't seem to be allowed any more. Are there any informations
about that?

Thanks Uli

Uli

>I updated EDB from 2.13 to 2.17 and got an error of unvalid column
>definitions.
>In a kind of crosstable I used "_22.2.201" as a column name e.g.
>
>That doesn't seem to be allowed any more. Are there any informations
>about that?

I think there's been some discussion on it (sorry can't remember the posts in question) and I think the problem in your case is the full stop which is also used to separate database and field names.

My personal view is that once its in quotes it should be anything goes, but I did agree with some of the comments made about restricting it.

Roy Lambert

Roy,

thanks, I must have missed these discussions.
Uli

On 6/2/2014 12:35 PM, Uli Becker wrote:
> I updated EDB from 2.13 to 2.17 and got an error of unvalid column
> definitions.
> In a kind of  crosstable I used "_22.2.201" as a column name e.g.
>
> That doesn't seem to be allowed any more. Are there any informations
> about that?

I believe it's incident 4029 - that one says database names but more
generically i believe applies to any identifiers

http://www.elevatesoft.com/incident?action=viewaddr&category=edb&release=2.17&incident=4029

Raul

Raul,

> I believe it's incident 4029 - that one says database names but more
> generically i believe applies to any identifiers
>
> http://www.elevatesoft.com/incident?action=viewaddr&category=edb&release=2.17&incident=4029

Thank you. Yes, that's probably the point.

Unfortunately it was not mentioned as a breaking change - and even
worse: a database with a table containing such a column definition can
NOT be opened any more.

The only way seems to be to reinstall an older version of EDB and change
the column definition(s) there.

Regards Uli

On 6/3/2014 3:21 AM, Uli Becker wrote:
> Unfortunately it was not mentioned as a breaking change - and even
> worse: a database with a table containing such a column definition can
> NOT be opened any more.
>

I went and looked at identifier spec
(http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=Identifiers)
and i find it confusing though punctuation might not be allowed.

However what you describe would be an issue though so hope Tim can work
something around it.

Raul

Raul,

> I went and looked at identifier spec
> (http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=Identifiers)
> and i find it confusing though punctuation might not be allowed.
>
> However what you describe would be an issue though so hope Tim can work
> something around it.

I submitted an incident report. Thanks.

Uli

Just to let you know:

The response to the incident report by Tim was, that periods are not allowed in identifiers since 2.17. And the only way to open an old database with such definitions is, to change these in an older version of EDB.

Uli