Think you will find there isn't
That's why there are several other initiatives like FileMakerStandards, or people who have gamely published their own internal standards..
And why asking a question on this forum about that stuff will being both lots of good opinions and a small rain of fire...
SQL does NOT play well with "_" ( underscores ) at the beginning of a field name...nor do numbers beginning fields names in SQL.
As Joshua has noted, underscores at the beginning of field names will error in SQL statements. So will field names with periods in them. There are also several reserved words that shouldn't be used as field names (a good list is here: List of SQL reserved words | Drupal.org ).
You can get around all of that by enclosing the field name in double quotes. However, it's generally easier to avoid the forbidden characters / words in the first place.
Thanks for the information guys. It's kind of surprising that FileMaker has not updated that document since 2005.
Does anyone have an specific example of where a period in a field name causes a problem with SQL statements (or any other conflict)? I am working with a developer that has used periods in almost every field name.
It's kind of surprising that FileMaker has not updated that document since 2005.
Why? The document may be “old”, but it is not outdated.
If you're concerned about intercommunication, consult documentation pertaining to the other platform(s), e.g. the official FM 13 SQL Reference, or the excellent SQL Guide created by Beverly Voth.
Does anyone have an specific example of where a period in a field name causes a problem with SQL statements
In SQL syntax, a period is the delimiter in a fully qualified field name; so a simple query like
SELECT myFieldName.WithAPeriod FROM SomeTO
will fail – unless (maybe) there is a table called “myFieldName” and a field called “WithAPeriod” …
SELECT DISTINCT YEAR(s."date")
FROM sales_related_sales AS s
WHERE s.amount > ?
ORDER BY s.amount DESC
whan you alias a table with the AS XXX you then access the fields with XXX.fieldname.
Thank you for the information.
The same applies even when you don't alias the table name.
SELECT DISTINCT YEAR ( sales_related_sales.date ) FROM sales_related_sales WHERE sales_related_sales.amount > ? ORDER BY sales_related_sales.amount DESC
is still valid.
(But then, who wants to type all that?)
Josh is correct. Naming within FileMaker alone allows all sorts of "conventions" that will break when used externally (not just SQL). Just don't do them. Look at FileMaker's recommendations:
for a good starting point. Me? I try to use alpha-numerics and underscore ONLY when naming anything including layouts, scripts and anything else that may be called outside of FileMaker.
I am working with a developer that has used periods in almost every field name.
That's quite unusual. Most of SQL engines would not let you do it, as far as I remember. A few NOSQL engines I used would not let you do it. Why use dot's in field names? If the developer came from a general programing background and is trying to use names like OOP syntax, he would not use it in variables or function names.