provide schemaMetaStructSQLite u Written for SQLite, but could support others u No macros u No code generatorsCreate Customers sqlite3 *sqldb; sqlite3_open(":memory:", &sqldb); ftsd::prepared_statement< bind_parameters(sqlite3_stmt *stmt, ParametersMetaStruct parameters) { int index = 1; meta_struct_for_each( [&](auto &m) mutable { auto r = bind_impl(stmt, index, m.value); check_sqlite_return(r parameters); }Reading SQL rows template auto read_row(sqlite3_stmt *stmt) { RowType row = {}; std::size_t count = sqlite3_column_count(stmt); auto size = meta_struct_size(row); assert(size

.unlock = pthread_mutex_unlock, .getsize = sqlite_usable_size, .nextitem = sqlite_pagecache_next, … }; #endifSimple SQL Database void sqlite_unlock(lock* l) { global_config.unlock(l); } pthread_mutex_unlockSimple SQL Database void sqlite_unlock(lock* l) { global_config.unlock(l); } void sqlite_getsize(void* p) { global_config.getsize(p); } void sqlite_nextitem(item* i) { global_config OpUmizaUons Benchmark Speedup Diff Size Change Summary memcached 9.39% -6, +2 removed unnecessary locks sqlite 25.60% -3, +3 removed DIY vtable implementa?on blackscholes 2.56% -61, +4 manual common subexpression

part of the file to reflect your database deployement. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish should look like: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_DIR, 'database.sqlite'), } } URL configuration You need to include the ’cms.urls’ urlpatterns

part of the file to reflect your database deployement. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_DIR, 'database.sqlite'), } } 2.1.2. URL configuration You need to include the 'cms

suggestions differ from the default, they’re highlighted below: • Database configuration (in URL format): sqlite://localhost/project.db • django CMS version: stable • Django version: 1.6 • Activate Django I18N part of the file to reflect your database deployment. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish should look like: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(BASE_DIR, 'database.sqlite'), } } Given django CMS’s support for Django 1.6.x, Django 1.7 (or later)

part of the file to reflect your database deployment. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish should look like: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_PATH, 'database.sqlite'), } } URL configuration You need to include the ’cms.urls’ urlpatterns

part of the file to reflect your database deployment. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish should look like: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_PATH, 'database.sqlite'), } } URL configuration You need to include the ’cms.urls’ urlpatterns

part of the file to reflect your database deployment. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish should look like: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_PATH, 'database.sqlite'), } } URL configuration You need to include the ’cms.urls’ urlpatterns

part of the file to reflect your database deployment. If you just want to try out things locally, sqlite3 is the easiest database to set up, however it should not be used in production. If you still wish DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(PROJECT_PATH, 'database.sqlite'), } } 1.2.2. URL configuration You need to include the 'cms

relational database backend. Each django CMS installation should have its own database. You can use SQLite, which is included in Python and doesn’t need to be installed separately or configured further. You DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': os.path.join(BASE_DIR , 'db.sqlite3'), } } Note For deployment, you’ll need to use a production-ready a minute for the migrations to run and will run integration tests against it. It will use testdb.sqlite as the database. If you want to start with a clean state you could use --clean argument. Some tests