Home
last modified time | relevance | path

Searched refs:active_schema (Results 1 – 13 of 13) sorted by relevance

/dports/irc/anope/anope-2.0.9/modules/extra/
H A Dm_sqlite.cpp43 std::map<Anope::string, std::set<Anope::string> > active_schema; member in SQLiteService
209 std::set<Anope::string> &known_cols = this->active_schema[table]; in CreateTable()
276 const std::set<Anope::string> &known_cols = this->active_schema[table]; in BuildInsert()
H A Dm_mysql.cpp109 std::map<Anope::string, std::set<Anope::string> > active_schema; member in MySQLService
369 std::set<Anope::string> &known_cols = this->active_schema[table]; in CreateTable()
425 const std::set<Anope::string> &known_cols = this->active_schema[table]; in BuildInsert()
/dports/graphics/py-gdal/gdal-3.3.3/doc/source/drivers/vector/
H A Dpg_advanced.rst30 *active_schema=* option.
33 can be overridden by specifying *active_schema=schema_name* within the
41 that you specify active_schema=bar_schema, 2 layers will be listed :
328 ogr2ogr -f PostgreSQL "PG:dbname=warmerda active_schema=apt200810" apt200810
352 convenient to use the active_schema connection string.
359 ogr2ogr -overwrite -f PostgreSQL "PG:dbname=warmerda active_schema=apt200810" apt200810
H A Dpg.rst194 the active_schema connection string. See below example.
/dports/graphics/p5-Geo-GDAL/gdal-3.3.3/doc/source/drivers/vector/
H A Dpg_advanced.rst30 *active_schema=* option.
33 can be overridden by specifying *active_schema=schema_name* within the
41 that you specify active_schema=bar_schema, 2 layers will be listed :
328 ogr2ogr -f PostgreSQL "PG:dbname=warmerda active_schema=apt200810" apt200810
352 convenient to use the active_schema connection string.
359 ogr2ogr -overwrite -f PostgreSQL "PG:dbname=warmerda active_schema=apt200810" apt200810
H A Dpg.rst194 the active_schema connection string. See below example.
/dports/graphics/gdal/gdal-3.3.3/doc/source/drivers/vector/
H A Dpg_advanced.rst30 *active_schema=* option.
33 can be overridden by specifying *active_schema=schema_name* within the
41 that you specify active_schema=bar_schema, 2 layers will be listed :
328 ogr2ogr -f PostgreSQL "PG:dbname=warmerda active_schema=apt200810" apt200810
352 convenient to use the active_schema connection string.
359 ogr2ogr -overwrite -f PostgreSQL "PG:dbname=warmerda active_schema=apt200810" apt200810
H A Dpg.rst194 the active_schema connection string. See below example.
/dports/irc/anope/anope-2.0.9/modules/
H A Dm_mysql.cpp109 std::map<Anope::string, std::set<Anope::string> > active_schema; member in MySQLService
369 std::set<Anope::string> &known_cols = this->active_schema[table]; in CreateTable()
425 const std::set<Anope::string> &known_cols = this->active_schema[table]; in BuildInsert()
/dports/deskutils/synapse/synapse-0.2.99.4/src/ui/
H A Dwidgets.vala387 private int active_schema = 0;
443 active_schema = i;
487 Gtk.Allocation[] alloc = schemas.get (active_schema).positions;
534 Gtk.Allocation[] alloc = schemas.get (active_schema).positions;
/dports/graphics/py-gdal/gdal-3.3.3/
H A DNEWS10616 active_schema=foo and schemas=foo[,bar] (#522 and #525)
/dports/graphics/p5-Geo-GDAL/gdal-3.3.3/
H A DNEWS10616 active_schema=foo and schemas=foo[,bar] (#522 and #525)
/dports/graphics/gdal/gdal-3.3.3/
H A DNEWS10616 active_schema=foo and schemas=foo[,bar] (#522 and #525)