| Commit message (Collapse) | Author | Age |
|
|
|
| |
fields.
|
|
|
|
| |
discussion we've decided to make the concatenation operator consistent with the other operators.
|
|
|
|
| |
arguments in wrong order.
|
|
|
|
| |
implement better security checks
|
|
|
|
| |
schema API
|
| |
|
|
|
|
| |
text for users, not text for developers; still keeping some debug information, if display_errors is turned on on the server
|
|
|
|
| |
(and removed spaces).
|
|
|
|
| |
accessible
|
|
|
|
| |
feature from schema API: load/save records based upon schema.
|
| |
|
|
|
|
| |
db_change_field() and friends in MySQL
|
|
|
|
| |
for evil (and mostly nothing else). We should not let contributed modules to easily break their database.
|
| |
|
|
|
|
| |
back to the original database function call, so we can provide a more accurate error message for DB errors
|
|
|
|
| |
near flowless updates
|
|
|
|
| |
Oracle and DB2. Also a performance improvement.
|
|
|
|
| |
Makes it work with DB2, Oracle, etc.
|
| |
|
|
|
|
| |
depending on the database engine used. Make the return value consistent across all supported database backends.
|
|
|
|
| |
in this development cycle; only whitespace changes
|
|
|
|
| |
statements and fixing a schema referencing bug
|
|
|
|
| |
using db_last_insert_id() instead of db_next_id().
|
| |
|
| |
|
|
|
|
| |
Oh, behave.
|
|
|
|
| |
snappy on Saturday evening.)
|
|
|
|
| |
core. Woot. Woot.
|
|
|
|
| |
documentation of db_next_id().
|
| |
|
|
|
|
| |
result was found. Consistent with PHP's mysql_result.
|
| |
|
|
|
|
| |
database abstraction layer and add extra rewriting needed only for Postgres.
|
|
|
|
| |
PostgreSQL. (Critical bug)
|
| |
|
| |
|
| |
|
|
|
|
| |
See: http://drupal.org/node/64279#t-placeholders
|
| |
|
| |
|
|
|
|
| |
et al: an initial install system for Drupal core.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
upgrade path for incorrectly set up databases)
|
|
|
|
| |
in presence of multiple database connections.
|
| |
|