wise-coders / dbschema

DbSchema Database Designer
https://dbschema.com
67 stars 3 forks source link

Field Names from FileMakerPro #39

Closed jimrandell closed 1 year ago

jimrandell commented 3 years ago

Hello and thank you for your help. I really like your product, and will enthusiastically purchase a license if I can resolve this blocker..

Using the Relational Data Explorer fails to display data, but it does returns a SQL Syntax error. Viewing the SQL History, the issue becomes clear to me: the SQL is failing due to two field names. The names of the troublesome fields are:

I can easily correct for this by pasting the failed SQL from the SQL History, into a new SQL Editor, and wrapping the field names in quotes, like this:

...but with dozens of tables, many with HUNDREDS of fields, I need a way for such fields to have quotes added automatically (exactly as happens with field names containing spaces. for example, in the SQL History, I see a field called: first name, automatically resolves to "first name").

I need a place to add "Rules for Auto-Quoting". You already have at least one such rule:

I need to add:

I suspect this already exists, but I cant find it. can you point me in the right direction, and perhaps give me some example syntax, in case i'm a bit too dim to figure it out myself?

Thank you so much for your assistance!!!!

dprutean commented 3 years ago

Thank you for reporting this issue. We will fix this right this week. A beta update will be available next Monday on https://dbschema.com/beta.php

jimrandell commented 3 years ago

Thank you guys! Been thinking about this....Filemaker allows some pretty funky character/strings to be used in field names, requiring developers to wrap double quotes around such field names when used in SQL.

some thoughts from someone familiar with FileMaker's idiosyncrasies:

...thank you for your help with this!!!

jimrandell commented 3 years ago

I have just downloaded and installed build 21043 and I see you have corrected one of the two issues I found:

this must be an illegal word. I'm not sure what other words may be illegal, and still suggest an option to wrap all field names in quotes.

wise-coders commented 1 year ago

Issue fixed in the next release.