ugh. It appears that #Postgres 15 changed the #ReservedKeywords, too, so I have project-wide issues needing a maybe-complex refactor of the word "state." Yeah, that one should have been obvious, but for years it worked for our US-serving program. It's Friday, and I'm sad.
@mkaatman no kidding. It's been three years since we designed the database, largely copying structure from a 15-year old MYSQL one, and because the domain needs billing addresses, we never stopped to think about the CS context. It seems that the newest Postgres versions have breaking changes in their handling of that word now.
@mkaatman @worldsendless STATE is not a keyword in any PostgreSQL version. It is a non-reserved word in the SQL standard.
@petereisentraut @mkaatman I think the problem is shown here https://www.postgresql.org/docs/current/sql-keywords-appendix.html
@petereisentraut @worldsendless okay I misunderstood the docs. I thought the absence of non-reserved meant reserved. Thanks for clarification.
@petereisentraut @mkaatman not reserved in postgres... My install begs to disagree
@worldsendless @petereisentraut What are you seeing exactly? I can't find any record of it being reserved.
@worldsendless That's a terrible keyword. I see it's part of sql:2023 but I can't find any explanation of what it's used for.