after a bit of fuss ... i fully shipped off EES at 8am today to Jason at Bren.
I'm dabbling in drupal at the moment in some core themeing components. I know that I will need at least 2 other things to do this week besides IDs site ... Sakai themeing or ASP->PHP are others items i'm aware of ... but not sure as to the resource locations. -dg On Oct 9, 2007, at 10:57 AM, Berger, Daniel wrote: > > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of >> Berger, Daniel >> Sent: Tuesday, October 09, 2007 11:15 AM >> To: camping-list@rubyforge.org >> Subject: RE: Session handling busted on Oracle >> >> >>> -----Original Message----- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED] On Behalf Of >>> Jonas Pfenniger >>> Sent: Monday, October 08, 2007 12:23 PM >>> To: camping-list@rubyforge.org >>> Subject: Re: Session handling busted on Oracle >>> >>> >>> 2007/10/8, Berger, Daniel <[EMAIL PROTECTED]>: >>>> Was there something else I should have used? >>> >>> Well technically, the id field is not necessary anymore. I >>> don't know how AR will react if it is set. Also, are you sure >>> that you are using camping from trunk ? >>> >>> Btw, here is the schema I have on sqlite : >>> >>> CREATE TABLE sessions ("hashid" varchar(32) NOT NULL, >>> "created_at" datetime DEFAULT NULL, "ivars" text DEFAULT NULL); >> >> Upon further review that isn't going to work. You can't set >> the @state variable without an id field. > > Upon further review of the previous review, it seems the problem is > not > the ID field, but the datatype of the ivars field. I went with this: > > CREATE TABLE sessions ( > id number primary key, > hashid varchar(32) NOT NULL, > created_at date DEFAULT NULL, > ivars varchar(256) DEFAULT NULL > ); > > So far, so good.... > > Regards, > > Dan > > > This communication is the property of Qwest and may contain > confidential or > privileged information. Unauthorized use of this communication is > strictly > prohibited and may be unlawful. If you have received this > communication > in error, please immediately notify the sender by reply e-mail and > destroy > all copies of the communication and any attachments. > _______________________________________________ > Camping-list mailing list > Camping-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list _______________________________________________ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
