diff dio_Mysql.tcl* 26c26 < if {[catch {package require mysqltcl}] \ ---if {[catch {package require Mysqltcl}] \51c51 < if {![lempty $host]} { lappend command -host $host } ---if {![lempty $host]} { lappend command $host }
I had actually fixed this and never committed it. The problem is that though we wrote the Mysql interface for DIO, no one ever did more than cursory testing of the whole thing. We're all Postgres guys here. 0-]
Trying the SESSION package with the Mysql database there were problems creating the session tables, the field names package, key and data are reserved words for Mysql, so I appended a '_' to the field names and modified the source accordingly. There were also problems using now as timestamp value, I have introduced a private variable now and fill that with a formatted string from Tcl clock format command . If you intend to integrate Oracle, you have to provide database specific code, because the date and time format is session specific there! Maybe it would be a good idea, to provide a getNow function in the DIO database specific code. The md5 code in my version needs a -hex option (see changelog of that package)
I plan to add Oracle support soon, but since I actually HAVE an Oracle database I can test against, we should be able to put something pretty solid together.
What problems did you have using 'now' as a timestamp variable? Mysql didn't like that?
Damon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
