Character Limits for Field Types

Jestor implements character limits on specific field types to optimize database performance and ensure efficient system usage. Understanding these limits will help you choose the right field type for your data.

Field Type Character Limits

Why These Limits Exist

Character limits serve two important purposes:

Database Performance: By limiting field sizes, Jestor can index and query data more efficiently. This results in faster loading times, quicker searches, and better overall system performance, especially as your database grows.

Appropriate Data Storage: These limits encourage proper field selection. Structured data like phone numbers, emails, and identification numbers don't require extensive character capacity, and limiting them prevents accidental misuse of field types.

When You Need More Characters

If you need to store longer content that exceeds these character limits, use the Long Text (Rich Text) field type instead. This field is designed for:

• Detailed descriptions
• Notes and comments
• Documentation
• Any text content requiring formatting or extended length

The Long Text field provides unlimited characters and supports rich formatting options like bold, italics, lists, and links.

Best Practices

• Use the appropriate field type for your data structure
• Reserve Long Text fields for genuinely long-form content
• Choose specific field types (CPF, CNPJ, Email, URL) over generic text fields when applicable
• This ensures optimal performance and maintains data consistency across your workspace

By respecting these character limits and choosing the right field types, you help maintain Jestor's speed and reliability as your processes scale.