Base Field Name Requirements

asked 2021-04-29 02:25:42 +0200

Ninpodeshi gravatar image

In the LO Getting Started Guide 6.0, it says "Field names are required to be single words." ("Step 4:" pg 247, near the bottom.) I searched elsewhere for confirmation but found nothing.

I have used multi word field names since I began with Base, and have not noticed any problems yet. But I primarily use Base's graphic user interface (GUI) for what I do. (I understand a little SQL, but not much.)

Is this a requirement just for SQL but not the GUI? In the GUI, should I use an underscore to connect field_names; could this prevent future problems?

Is there a place that lists different requirements of DB elements that I should look to in the future? Are those in the Base guide? (I'm reading the LO Base Guide now, but it suggested reading this chapter in the Getting Started Guide.)

edit retag flag offensive close merge delete



Although not a requirement, it appears the documentation is incorrect. You should avoid field or file or directory (etc) names containing spaces. Will make your life more difficult.

When dealing with databases, refer to the specific documentation for that database. LO does not provide that and you have not stated yours.

Ratslinger gravatar imageRatslinger ( 2021-04-29 02:45:42 +0200 )edit

Ratslinger, I'm not sure if you're Superman, but you're definitely faster than a speeding bullet.

My apologies, I forgot to specify that I'm using HSQL with Base. I searched this question specifically with HSQL before I came here. Holding off on Firebird until it's more stable.

It's easy enough to use an _underscore_ instead of a space, so I'll make a habit of it. Thank you for confirming.

Ninpodeshi gravatar imageNinpodeshi ( 2021-04-29 04:15:08 +0200 )edit