MediaWiki REL1_30
|
Functions | |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN boolean columns are always mapped to as the code does not always treat the column as a | boolean (which is limited to accepting true, false, 0, 1, t, or f) *The default data type for all VARCHAR |
Variables | |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN boolean columns are always mapped to as the code does not always treat the column as a | CHAR |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN boolean columns are always mapped to as the code does not always treat the column as a and VARBINARY columns should simply be TEXT The only exception is when VARBINARY is used to store true binary such as the math_inputhash | column |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the | conversion |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN boolean columns are always mapped to as the code does not always treat the column as a and VARBINARY columns should simply be TEXT The only exception is when VARBINARY is used to store true binary | data |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well | integrated |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of | life |
This document describes the state of Postgres support in | MediaWiki |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN boolean columns are always mapped to | SMALLINT |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss | Still |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres | support |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN | type |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN boolean columns are always mapped to as the code does not always treat the column as a boolean | ( | which is limited to accepting | true, |
false | , | ||
0 | , | ||
1 | , | ||
t | , | ||
or | f ) |
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN boolean columns are always mapped to as the code does not always treat the column as a CHAR |
Definition at line 41 of file postgres.txt.
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN boolean columns are always mapped to as the code does not always treat the column as a and VARBINARY columns should simply be TEXT The only exception is when VARBINARY is used to store true binary such as the math_inputhash column |
Definition at line 44 of file postgres.txt.
Referenced by MonoBookTemplate::execute().
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the conversion |
Definition at line 28 of file postgres.txt.
array $mLimitReportData Parser limit report ParserOutput::data |
Definition at line 43 of file postgres.txt.
Referenced by MessageCache::load().
This document describes the state of Postgres support in and is fairly well maintained The main code is very well integrated |
Definition at line 8 of file postgres.txt.
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of life |
Definition at line 18 of file postgres.txt.
those of us who don t want or need it can just leave it out The extensions don t even have to be shipped with MediaWiki |
Definition at line 1 of file postgres.txt.
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around* Although Postgres has a true BOOLEAN boolean columns are always mapped to SMALLINT |
Definition at line 37 of file postgres.txt.
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss Still |
Definition at line 9 of file postgres.txt.
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres support |
Definition at line 11 of file postgres.txt.
< input type="submit" name="fulltext" class="mw-ui-button" value="Search full text"/></p ></form ></div > !end !test InputBox type |
Definition at line 36 of file postgres.txt.
Referenced by Exif::__construct(), ProtectedPagesPager::__construct(), ChangesFeed::__construct(), SearchIndexFieldDefinition::__construct(), PoolCounterWork::__construct(), LogPage::__construct(), ManualLogEntry::__construct(), JobSpecification::__construct(), Site::__construct(), JSNode::__construct(), MediaWiki\Auth\Throttler::__construct(), MediaWiki\Widget\DateTimeInputWidget::__construct(), ChangesListFilterGroup::__construct(), JobQueue::__construct(), LogPage::addEntry(), JobQueue::batchPush(), JobQueueDB::claimOldest(), JobQueueDB::claimRandom(), MediaWiki\Auth\Throttler::clear(), JobQueueDB::doAck(), JobQueueRedis::doAck(), JobQueueRedis::doBatchPush(), JobQueueDB::doBatchPushInternal(), JobQueueDB::doDelete(), JobQueueMemory::doDelete(), JobQueueDB::doIsEmpty(), JobQueueDB::doPop(), JobQueueRedis::doPop(), JobQueueRedis::encodeQueueName(), ChangesFeed::execute(), SpecialUnblock::execute(), SkinFallbackTemplate::execute(), UpdateLogging::execute(), JSParser::Expression(), JobQueueDB::getCacheKey(), LogPage::getDescription(), MediaWiki\Widget\DateTimeInputWidget::getInputElement(), File::getIsSafeFileUncached(), RedisLockManager::getLocksOnServer(), LogPage::getName(), ProtectedPagesPager::getQueryInfo(), JobQueueMemory::getQueueData(), Block::getRangeEnd(), Block::getRangeStart(), LogPage::getRestriction(), JobQueue::getRootJobCacheKey(), Gadget::getType(), MediaWiki\Auth\Throttler::increase(), SearchIndexFieldDefinition::merge(), Block::newLoad(), AtomFeed::outHeader(), AtomFeed::outItem(), JobQueue::pop(), JobQueueDB::recycleAndDeleteStaleJobs(), LogPage::saveContent(), MonoBookTemplate::searchBox(), SpecialBlock::setParameter(), Block::setTarget(), WikiRevision::setType(), LogEventsList::showLogExtract(), and JSParser::Statement().