WebDB
Links
  • 👋Welcome to WebDB Documentation
  • Installation
    • 1️⃣Standalone
    • 🔢Compose
    • ☸️K8S
    • 🖥️Native
    • 🛡️Security
    • ❌Uninstall
  • Connection
    • DBMS Discovery
    • Credentials Guessing
    • SSH Tunnel
  • Database
  • Interface
    • Schema
    • Database
    • Table
    • Relations
    • Structure
    • Offline
    • Symbols
    • Configuration
  • Explore
    • Explore
    • Search
    • Update
    • Batch Update
  • Query
    • Editor
      • Autocomplete
  • Structure
    • NoSQL inferring limitation
  • Insert
    • Generator
    • Framework embed
    • Foreign Key / Enum
    • Autocomplete
    • Error
  • Monitoring
    • Stats
    • Process List
  • Time machine
  • Compare
  • Blob
  • Encoding / Collation
  • Complexes
  • Backend
    • Configuration
    • Data storage
    • Docker container
  • Compatibility
  • More
    • Offline
    • Business Model
    • Alternatives
Powered by GitBook
On this page
  • IDs (database/table/column/index name)
  • Connection Encoding
  • Values

Was this helpful?

Encoding / Collation

IDs (database/table/column/index name)

Database server handle quite well special character, whether database name itself or table table or columns name.

WebDB escape them well. However, for your own interest, the UI don't allow special character input and tell you

Connection Encoding

From 2024, all server set the default collation to a very UTF-8 compatible, so you don't have to worry are different alphabet or special characters

WebDB, by default, let driver choose encoding for the connection. All implemented driver, until now, use UTF-8 as default encoding

Values

On this side, you are obviously free to input any characters, anywhere on the App.

WebDB backend will escape any quote and special symbols before generating queries

PreviousBlobNextComplexes

Last updated 1 year ago

Was this helpful?