Dynamically Typed Value Object body { margin: auto; font-family: "Verdana" "sans-serif"; padding: 8px 1%; } a { color: #45735f } a:visited { color: #734559 } .logo { position:absolute; margin:3px; } .tagline { float:right; text-align:right; font-style:italic; width:240px; margin:12px; margin-top:58px; } .toolbar { font-variant: small-caps; text-align: center; line-height: 1.6em; margin: 0; padding:1px 8px; } .toolbar a { color: white; text-decoration: none; padding: 6px 12px; } .toolbar a:visited { color: white; } .toolbar a:hover { color: #80a796; background: white; } .content { margin: 5%; } .content dt { font-weight:bold; } .content dd { margin-bottom: 25px; margin-left:20%; } .content ul { padding:0px; padding-left: 15px; margin:0px; } /* rounded corners */ .se { background: url(../images/se.png) 100% 100% no-repeat #80a796} .sw { background: url(../images/sw.png) 0% 100% no-repeat } .ne { background: url(../images/ne.png) 100% 0% no-repeat } .nw { background: url(../images/nw.png) 0% 0% no-repeat } border="0"> Small. Fast. Reliable.Choose any three. About Sitemap Documentation Download License News Developers Support SQLite C Interface Dynamically Typed Value Object typedef struct Mem sqlite3_value; SQLite uses the sqlite3_value object to represent all values that can be stored in a database table. SQLite uses dynamic typing for the values it stores. Values stored in sqlite3_value objects can be be integers, floating point values, strings, BLOBs, or NULL. An sqlite3_value object may be either "protected" or "unprotected". Some interfaces require a protected sqlite3_value. Other interfaces will accept either a protected or an unprotected sqlite3_value. Every interface that accepts sqlite3_value arguments specifies whether or not it requires a protected sqlite3_value. The terms "protected" and "unprotected" refer to whether or not a mutex is held. A internal mutex is held for a protected sqlite3_value object but no mutex is held for an unprotected sqlite3_value object. If SQLite is compiled to be single-threaded (with SQLITE_THREADSAFE=0 and with sqlite3_threadsafe() returning 0) then there is no distinction between protected and unprotected sqlite3_value objects and they can be used interchangable. However, for maximum code portability it is recommended that applications make the distinction between between protected and unprotected sqlite3_value objects even if they are single threaded. The sqlite3_value objects that are passed as parameters into the implementation of application-defined SQL functions are protected. The sqlite3_value object returned by sqlite3_column_value() is unprotected. Unprotected sqlite3_value objects may only be used with sqlite3_result_value() and sqlite3_bind_value(). All other interfaces that use sqlite3_value require protected sqlite3_value objects. See also lists of Objects, Constants, and Functions. This page last modified 2008/05/12 13:08:44 UTC
