And after stresstesting a 1000 connections it appeared again.
Thist time it throws
invalid command name "::DIO::Tdbc"
while executing
"::DIO::Tdbc DIO Sqlite3 -db session.db"
(in namespace eval "::request" script line 6)
invoked from within
"namespace eval ::request $script"
("::try" body line 12)
While the other times it works without problems.
Sorry for the multiple messages, as i thought the error disappeared
but reappears without specific reproducible workflows again.
Greetings
Quoting [email protected]:
Hello everyone,
so the error appeared again randomly.
I replaced
::DIO::handle Tdbc Sqlite3 DIO -db "session.db"
with
::DIO::Tdbc DIO Sqlite3 -db session.db
and it seems to work stable now.
I think this is becouse of the default DIO instance name used that
has the same name as the Package.
as stated in the documentation
dioObject
The name of the DIO object we'll use to access the database (default DIO)
Greetings, Louis
Quoting [email protected]:
Excuse me calling it like this:
package require sqlite3
package require Session
package require DIO
::DIO::handle Tdbc Sqlite3 ::DIO -db "session.db"
Greetings
Quoting [email protected]:
Defining DIO like this solved the error:
::DIO::handle ::DIO::Tdbc ::Sqlite3 ::DIO -db "session.db"
Greetings Louis
Quoting [email protected]:
Hello Everyone,
I encountered a bug that appears sometimes while loading a simple
session example site.
command "DIO" already exists in namespace "::"
while executing
"::itcl::parser::handleClass ::DIO::Tdbc ::DIO::Tdbc DIO Sqlite3
-db session.db"
invoked from within
"::DIO::Tdbc DIO Sqlite3 -db session.db"
("uplevel" body line 1)
invoked from within
"uplevel \#0 ::DIO::$interface $obj $tdbc_driver {*}$args"
(procedure "::DIO::handle" line 24)
invoked from within
"::DIO::handle Tdbc Sqlite3 DIO -db "session.db""
(in namespace eval "::request" script line 6)
invoked from within
"namespace eval ::request $script"
("::try" body line 12)
CODE:
package require sqlite3
package require Session
package require DIO
::DIO::handle Tdbc Sqlite3 DIO -db "session.db"
Session SESSION -debugMode 0
SESSION activate
Currently trying to solve this.
Thank you
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
