Search for all
| Title | Object type | File name | Summary |
|---|---|---|---|
| DatabaseFetchTestCase::testQueryFetchDefault | function | modules/ |
Confirm that we can fetch a record properly in default object mode. |
| DatabaseFetchTestCase::testQueryFetchObject | function | modules/ |
Confirm that we can fetch a record to an object explicitly. |
| DatabaseInsertDefaultsTestCase | class | modules/ |
Insert tests for "database default" values. |
| DatabaseInsertDefaultsTestCase::getInfo | function | modules/ |
|
| DatabaseInsertDefaultsTestCase::testDefaultEmptyInsert | function | modules/ |
Test that no action will be preformed if no fields are specified. |
| DatabaseInsertDefaultsTestCase::testDefaultInsert | function | modules/ |
Test that we can run a query that is "default values for everything". |
| DatabaseInsertDefaultsTestCase::testDefaultInsertWithFields | function | modules/ |
Test that we can insert fields with values and defaults in the same query. |
| DatabaseInsertLOBTestCase | class | modules/ |
Insert tests using LOB fields, which are weird on some databases. |
| DatabaseInsertLOBTestCase::getInfo | function | modules/ |
|
| DatabaseInsertLOBTestCase::testInsertMultipleBlob | function | modules/ |
Test that we can insert multiple blob fields in the same query. |
| DatabaseInsertLOBTestCase::testInsertOneBlob | function | modules/ |
Test that we can insert a single blob field successfully. |
| DatabaseInsertTestCase | class | modules/ |
Test the insert builder. |
| DatabaseInsertTestCase::getInfo | function | modules/ |
|
| DatabaseInsertTestCase::testInsertFieldOnlyDefinintion | function | modules/ |
Test that we can specify fields without values and specify values later. |
| DatabaseInsertTestCase::testInsertLastInsertID | function | modules/ |
Test that inserts return the proper auto-increment ID. |
| DatabaseInsertTestCase::testInsertSelectAll | function | modules/ |
Tests that the INSERT INTO ... SELECT * ... syntax works. |
| DatabaseInsertTestCase::testInsertSelectFields | function | modules/ |
Test that the INSERT INTO ... SELECT (fields) ... syntax works. |
| DatabaseInsertTestCase::testMultiInsert | function | modules/ |
Test that we can insert multiple records in one query object. |
| DatabaseInsertTestCase::testRepeatedInsert | function | modules/ |
Test that an insert object can be reused with new data after it executes. |
| DatabaseInsertTestCase::testSimpleInsert | function | modules/ |
Test the very basic insert functionality. |
| DatabaseInvalidDataTestCase | class | modules/ |
Test invalid data handling. |
| DatabaseInvalidDataTestCase::getInfo | function | modules/ |
|
| DatabaseInvalidDataTestCase::setUp | function | modules/ |
Sets up a Drupal site for running functional and integration tests. |
| DatabaseInvalidDataTestCase::testInsertDuplicateData | function | modules/ |
Traditional SQL database systems abort inserts when invalid data is encountered. |
| DatabaseLog | class | includes/ |
Database query logger. |
| DatabaseLog::$connectionKey | property | includes/ |
The connection key for which this object is logging. |
| DatabaseLog::$queryLog | property | includes/ |
Cache of logged queries. This will only be used if the query logger is enabled. |
| DatabaseLog::clear | function | includes/ |
Empty the query log for the specified logging key. |
| DatabaseLog::end | function | includes/ |
Stop logging for the specified logging key. |
| DatabaseLog::findCaller | function | includes/ |
Determine the routine that called this query. |
| DatabaseLog::get | function | includes/ |
Retrieve the query log for the specified logging key so far. |
| DatabaseLog::log | function | includes/ |
Log a query to all active logging keys. |
| DatabaseLog::start | function | includes/ |
Begin logging queries to the specified connection and logging key. |
| DatabaseLog::__construct | function | includes/ |
Constructor. |
| DatabaseLoggingTestCase | class | modules/ |
Query logging tests. |
| DatabaseLoggingTestCase::getInfo | function | modules/ |
|
| DatabaseLoggingTestCase::testEnableLogging | function | modules/ |
Test that we can log the existence of a query. |
| DatabaseLoggingTestCase::testEnableMultiConnectionLogging | function | modules/ |
Test that we can log queries separately on different connections. |
| DatabaseLoggingTestCase::testEnableMultiLogging | function | modules/ |
Test that we can run two logs in parallel. |
| DatabaseLoggingTestCase::testEnableTargetLogging | function | modules/ |
Test that we can log queries against multiple targets on the same connection. |
| DatabaseLoggingTestCase::testEnableTargetLoggingNoTarget | function | modules/ |
Test that logs to separate targets collapse to the same connection properly. |
| DatabaseMergeTestCase | class | modules/ |
Test the MERGE query builder. |
| DatabaseMergeTestCase::getInfo | function | modules/ |
|
| DatabaseMergeTestCase::testInvalidMerge | function | modules/ |
Test that an invalid merge query throws an exception like it is supposed to. |
| DatabaseMergeTestCase::testMergeInsert | function | modules/ |
Confirm that we can merge-insert a record successfully. |
| DatabaseMergeTestCase::testMergeInsertWithoutUpdate | function | modules/ |
Test that we can merge-insert without any update fields. |
| DatabaseMergeTestCase::testMergeUpdate | function | modules/ |
Confirm that we can merge-update a record successfully. |
| DatabaseMergeTestCase::testMergeUpdateExcept | function | modules/ |
Confirm that we can merge-update a record successfully, with different insert and update. |
| DatabaseMergeTestCase::testMergeUpdateExplicit | function | modules/ |
Confirm that we can merge-update a record successfully, with alternate replacement. |
| DatabaseMergeTestCase::testMergeUpdateExpression | function | modules/ |
Confirm that we can merge-update a record successfully, with expressions. |
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.