World: r3wp

it should work if your DB driver supports it, DO-SQL is just a higher 
level wrapper.

Graham: cookies specification says that if domain attribut in cookie, 
is not provided, "The default value of domain is the host name of 
the server which generated the cookie response."

Graham: it seems that I've found a bug the session expiration in 
Cheyenne, that might be the cause of your error. It's now fixed. 
I'm testing it a little more before releasing it, I'd like to fix 
the cookies issues of Brian and Terry too (one way or another, these 
issues must be related to the info Cheyenne is sending back in the 
response).

Thanks.

qry: [ {select fnames, surname, uid from users where userid = "?" 
and pass = "?" and activ = 'T'} in-user in-pass ]
			sql: do-sql 'remr qry
gives me this

Error Code :  	329
Description : 	script error !

ODBC error: Dynamic SQL Error SQL error code = -206 Column unknown 
? At line 1, column 59.
Near : 	[insert port data 
copy port
]
Where : 	do-sql

but this works;


   qry: rejoin [ "select fnames, surname, uid from users where userid 
   = '" in-user "' and pass = '" in-pass "' and activ = 'T'" ]
			sql: do-sql 'remr qry

oops  ...

ignore

Seems that I found the guilty for the weird session cookie issues, 
need to dig up a little more to confirm the theory.

I'm seeing this after successful inserts 


{make object! [ code: 329 type: 'script id: 'bad-bad arg1: "ODBC" 
arg2: "Invalid cursor state" arg3: none near: [copy port] where: 
'do-sql ]}

where no recordset is being returned

that's coming from the ODBC driver

Yes.

The insert is occuring okay.

but I get this error

so, is cheyenne querying the database after the query expecting a 
response ?

I can bypass the error by wrapping an attempt around the sql insert

do-sql is doing an INSERT on the database port, then a COPY on the 
port. Does your query only require an INSERT on the port and no COPY 
?

let me check RT's doc about that.

Yes, only an insert

/remote-ip is picking up the router address .. anyway to get the 
actual remote ip address?

must be because the remote-ip appears in the logs

if the client is behind a router and has a local IP NAT-ed by the 
router, no way.

RT's documentation about databases drivers doesn't say what 'insert 
is supposed to return ? Could you tell me that ?

it returns nothing

I never do a copy on a db-port after an insert

you mean after an SQL INSERT or the REBOL 'insert  ?

>> insert p [ {insert into weblog (remoteip) values (?)} "127.0.0.1" 
]
>> copy p
** Script Error: ODBC error: Invalid cursor state
** Near: copy p

ok, I see now.

There's a workaround until I publish the next release (later tonight), 
use : insert databases/remr query

Ok.

databases/remr is pointing to the opened port to the DB server.

Cheyenne has again crashed on me .. leaving one process running.

same error as before ?

No error seen.

the other two processes just died.

can we log this to a local log file ?

you should try with changing the Cheyenne.r encap header to this 
one :

Encap: [no-window quiet secure none title "Cheyenne"]

it will work even if not encapped

but I'm not running encap

oh ?? really?

Ok, try

the 'no-window option will trigger file logging mode

ahh.

it is tested in cheyenne.r startup code and if defined, it will try 
to catch all errors in a local %crash.log file

Hope we aren't giving u too much work!

Not at all Graham, I should thank you for making a big leap forward 
to Cheyenne's stability and reliability. :-)

:)

The session cookie problem is related to incorrect timezone calculation 
in cookies expire time. I'm making a fix for Cheyenne, but due to 
a REBOL bug on Windows (http://www.rebol.net/cgi-bin/upnews.r?view=0005), 
I can't find an easy solution for that platform...

So I guess that I'll add a config option for setting the correct 
timezone for Windows users manually and for /Pro users, I'll support 
the GetTimeZoneInformation() win32 function for automatic setting.