On 19 Jul 2019, at 9:15pm, Gilles Pérez wrote:
> Is it possible in Tcl to specify I want a boolean?
You don't want a boolean. SQLite doesn't understand booleans. You want
integers. Do this
Constants:
DB_FALSE = 0, DB_TRUE = 1
I would suggest you don't use names like SQLITE_FALSE
2019-07-19 19:29 +02:00, d...@sqlite.org :
> On 7/19/19, Gilles Pérez wrote:
> > set tvalue true
>
> This statement sets the TCL variable "tvalue" to the four-character
> string "true", not to a boolean true.
Is it possible in Tcl to specify I want a boolean? For now, I “filter”
true/false
On 7/19/19, Gilles Pérez wrote:
> set tvalue true
This statement sets the TCL variable "tvalue" to the four-character
string "true", not to a boolean true.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
As the script got removed, here it is:
package require sqlite3
proc main {} {
puts "sqlite3 version: [
exec sqlite3 -version
]"
sqlite3 db :memory:
puts "libsqlite3 version: [
db version
]"
db eval {
Hello,
If I run the attached script (results I see in attached text), one can see a
problem with true and false in variables. If I write true or false directly, no
problem, sqlite store a 1 or a 0.
But if a put them in a variable, sqlite always store them as strings "true" or
"false".
How
5 matches
Mail list logo
