- Language: en
22 results for mysql in version 4.0
-
Database Functions
- … MySQL may be converted to an incorrect type unless explicitly cast to the correct database …
-
Model Meta options
- … MySQL backend. See the MySQL notes for more details. Table name quoting for Oracle In order …
-
Constraints reference
- … MySQL, MariaDB, and SQLite. Deferrable unique constraints are ignored on MySQL, MariaDB, and SQLite as neither …
-
GeoDjango Installation
- … MySQL, Oracle, and SQLite (with SpatiaLite) are the spatial databases currently supported. Note PostGIS is recommended …
-
django.contrib.auth
- … MySQL with the utf8mb4 encoding (recommended for proper Unicode support), specify at most max_length …
-
Unicode data
- … MySQL users, refer to the MySQL manual for details on how to set or alter …
-
Query Expressions
- … mysql ( self , compiler , connection , ** extra_context ): return super () . as_sql ( compiler , connection , function = 'CONCAT …
-
Model field reference
- … MySQL 5.7.8+, Oracle, PostgreSQL, and SQLite (with the JSON1 extension enabled ). JSONField. encoder An optional …
-
Lookup API reference
- … mysql for Django’s built-in backends. get_lookup ( lookup_name ) Must return the lookup …
-
GeoDjango Tutorial
- … MySQL, and Oracle databases. shp2pgsql : This utility included with PostGIS imports ESRI shapefiles into PostGIS …
-
Migration Operations
- … MySQL and Oracle). This should be safe, but may cause a crash if you attempt …
-
Installing Geospatial libraries
- … MySQL or Oracle as the spatial database, only GEOS is required. Note On Linux platforms …
