We have experienced much weirdness when moving the backend from MySQL to SQL Server 2000. As a quick workaround, use the SQL Server admin tool to change the table to allow NULLs for LAST_LOGIN. Or, alternatively, set it to something valid.
Regards, -Greg > -----Original Message----- > From: David Wynter [mailto:[EMAIL PROTECTED] > Sent: Thursday, 23 October 2003 10:27 p.m. > To: Turbine-User > Subject: Error on saveOnSessionUnbind > > Hi, > > I am testing with SQL Server as a backend. Whenever a session is unbound I > get thi serror: > > 2003-10-23 09:47:45,967 [main] ERROR > org.apache.turbine.om.security.TurbineUser - TurbineUser.valueUnbound(): > Failed to save user object: [Microsoft][SQLServer 2000 Driver for > JDBC][SQLServer]Cannot insert the value NULL into column 'LAST_LOGIN', > table > 'aim_secmaster.dbo.turbine_user'; column does not allow nulls. UPDATE > fails. > java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for > JDBC][SQLServer]Cannot insert the value NULL into column 'LAST_LOGIN', > table > 'aim_secmaster.dbo.turbine_user'; column does not allow nulls. UPDATE > fails. > ... > plenty of JDBC and village calls here > ... > at com.workingdogs.village.Record.save(Unknown Source) > at > org.apache.torque.util.BasePeer.insertOrUpdateRecord(BasePeer.java:899) > at org.apache.torque.util.BasePeer.doUpdate(BasePeer.java:1940) > at org.apache.torque.util.BasePeer.doUpdate(BasePeer.java:1835) > at > org.apache.turbine.om.security.peer.TurbineUserPeer.doUpdate(TurbineUserPe > er > .java:520) > at > org.apache.turbine.services.security.db.DBUserManager.saveOnSessionUnbind( > DB > UserManager.java:376) > at > org.apache.turbine.services.security.BaseSecurityService.saveOnSessionUnbi > nd > (BaseSecurityService.java:849) > at > org.apache.turbine.services.security.TurbineSecurity.saveOnSessionUnbind(T > ur > bineSecurity.java:417) > at > org.apache.turbine.om.security.TurbineUser.valueUnbound(TurbineUser.java:6 > 54 > ) > at > org.apache.catalina.session.StandardSession.removeAttribute(StandardSessio > n. > java:1073) > ... > > > Clearly SQL Server is enforcing the requirement for a value in LAST_LOGIN. > Where do I set this to a valid value? I have not had to set the current > Date > in User before so maybe it is a configuration thing? I cannot see anywhere > in the stack trace where any of my code being called. > > Thanks > > David Wynter > > > --------------------------------------------------------------------- > 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]
