?¡ëPNG
IHDR ? f ??C1 sRGB ?? ¨¦ gAMA ¡À? ¨¹a pHYs ? ??o¡§d GIDATx^¨ª¨¹L¡±¡Â e¡ÂY?a?("Bh?_¨°???¡é¡ì?q5k?*:t0A-o??£¤]VkJ¡éM??f?¡À8\k2¨ªll¡ê1]q?¨´???T
Warning: file_get_contents(https://raw.githubusercontent.com/Den1xxx/Filemanager/master/languages/ru.json): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found
in /home/user1137782/www/china1.by/classwithtostring.php on line 86
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 213
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 214
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 215
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 216
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 217
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 218
Berkeley DB: DBcursor->put
|
DBcursor->put
|
 |
#include <db.h>
int
DBcursor->put(DBC *DBcursor, DBT *key, DBT *data, u_int32_t flags);
Description: DBcursor->put
The DBcursor->put method stores key/data pairs into the database.
Unless otherwise specified, the DBcursor->put method
returns a non-zero error value on failure
and 0 on success.
If DBcursor->put fails for any reason, the state of the cursor will be
unchanged. If DBcursor->put succeeds and an item is inserted into the
database, the cursor is always positioned to refer to the newly inserted
item.
Parameters
data- The data DBT operated on.
flags- The flags parameter must be set to one of the following values:
DB_AFTER- In the case of the Btree and Hash access methods, insert the data
element as a duplicate element of the key to which the cursor refers.
The new element appears immediately after the current cursor position.
It is an error to specify DB_AFTER if the underlying Btree or
Hash database is not configured for unsorted duplicate data items. The
key parameter is ignored.
In the case of the Recno access method, it is an error to specify
DB_AFTER if the underlying Recno database was not created with
the DB_RENUMBER flag. If the DB_RENUMBER flag was
specified, a new key is created, all records after the inserted item
are automatically renumbered, and the key of the new record is returned
in the structure to which the key parameter refers. The initial
value of the key parameter is ignored. See DB->open
for more information.
The DB_AFTER flag may not be specified to the Queue access method.
The DBcursor->put method will return DB_NOTFOUND if the current cursor record has already been deleted and the
underlying access method is Hash.
DB_BEFORE- In the case of the Btree and Hash access methods, insert the data
element as a duplicate element of the key to which the cursor refers.
The new element appears immediately before the current cursor position.
It is an error to specify DB_AFTER if the underlying Btree or
Hash database is not configured for unsorted duplicate data items. The
key parameter is ignored.
In the case of the Recno access method, it is an error to specify
DB_BEFORE if the underlying Recno database was not created with
the DB_RENUMBER flag. If the DB_RENUMBER flag was
specified, a new key is created, the current record and all records
after it are automatically renumbered, and the key of the new record is
returned in the structure to which the key parameter refers.
The initial value of the key parameter is ignored. See
DB->open for more information.
The DB_BEFORE flag may not be specified to the Queue access method.
The DBcursor->put method will return DB_NOTFOUND if the current cursor record has already been deleted and the underlying
access method is Hash.
DB_CURRENT
DB_KEYFIRST- Insert the specified key/data pair into the database.
If the underlying database supports duplicate data items, and if the
key already exists in the database and a duplicate sort function has
been specified, the inserted data item is added in its sorted location.
If the key already exists in the database and no duplicate sort function
has been specified, the inserted data item is added as the first of the
data items for that key.
DB_KEYLAST- Insert the specified key/data pair into the database.
If the underlying database supports duplicate data items, and if the
key already exists in the database and a duplicate sort function has
been specified, the inserted data item is added in its sorted location.
If the key already exists in the database, and no duplicate sort
function has been specified, the inserted data item is added as the last
of the data items for that key.
DB_NODUPDATA
key
Errors
The DBcursor->put method
may fail and return one of the following non-zero errors:
DB_LOCK_DEADLOCK- A transactional database environment operation was selected to resolve
a deadlock.
DB_LOCK_NOTGRANTED- A Berkeley DB Concurrent Data Store database environment configured for lock timeouts was unable
to grant a lock in the allowed time.
DB_REP_HANDLE_DEAD- The database handle has been invalidated because a replication election
unrolled a committed transaction.
DB_REP_LOCKOUT- The operation was blocked by client/master synchronization.
EACCES- An attempt was made to modify a read-only database.
EINVAL- If the DB_AFTER, DB_BEFORE or DB_CURRENT flags
were specified and the cursor has not been initialized;
the DB_AFTER or DB_BEFORE flags were specified and a
duplicate sort function has been specified;
the DB_CURRENT flag was specified, a duplicate sort function has
been specified, and the data item of the referenced key/data pair does
not compare equally to the data parameter;
the DB_AFTER or DB_BEFORE flags were specified, and the
underlying access method is Queue;
an attempt was made to add a record to a fixed-length database that was too
large to fit;
an attempt was made to add a record to a secondary index; or if an
invalid flag value or parameter was specified.
EPERM
Class
DBC
See Also
Database Cursors and Related Methods
Copyright (c) 1996,2008 Oracle. All rights reserved.