neatComponents - Useful naming conventions

	clearString neatComponents Documentation
	Getting Started The neatComponents Guide Building & Styling Applications A first app walkthrough Functionality Components Actions Datatypes Application Development Data Integration Process Management Introduction to Process Management Techniques Designing a Process Management system Defining Flow State Validation Auditing and Monitoring Performance and Scale Scaling and Clustering Events AI Integration E-commerce Site security - users and permissions How-to Resources How-To Resources Techniques & KB Articles Advertising Voting System Profiles Search Engine Optimisation Making sites Accessible Managing discussions Mobile Sites Installing Installing neatComponents Upgrading Upgrade Protection Release notes Support Services Making Payments Product Support System Analysis & Design Onboarding Partnering Reselling Apps (SaaS) The VARs Guide
	Useful naming conventions

neatComponents is the hybrid-cloud database engine that powers clearString.
Previous page	Data Integration	Next page
Useful naming conventions

Whilst you can give a Table any name you like, it is usually best to use a singular noun, eg:

Product
Vehicle
Plant

Copyright © 2025 Enstar LLC All rights reserved

Print this page

Translate:


Created: 6 September 2025 12:33:29
Version: 1.9.6543
Ref: 4345 p
Build Time (ms): 141