Thanks. This definitely helps.
-----Original Message----- From: Ray Sprinkle [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 28, 2005 5:46 AM To: Slide Users Mailing List Subject: RE: Slide User Base & Oracle Support I am successfully running Oracle with Slide 2.1 (patched) in a production environment now. It works fine but there are still a few problems (limitations) with the latest Oracle support in Slide: 1. Properties cannot exceed the maxium length of a varchar2 2. Properties cannot exceed 4000 bytes. 3. Property search performance To solve problem 1 you can change the Slide schema to use CLOBs instead of varchar2s. Solving problem 1 runs you into problem 2. Problem 2 is related to Oracle's JDBC driver only being able to bind 4000 bytes in a setString() operation. I am running with CLOBs on Oracle now, and I have a tentative patch (completely untested) for fixing problem 2 that I will be testing shortly. It requires copying the relevant method from the generic rdbms store to the oracle store and changing the setString method to one that uses the JDBC stream interface. As for problem 3, I don't think you can use the expression optimization package (can't remember the name) for property searching because Oracle will not allow a 'LIKE' comparison on a CLOB. I run into these problems right now with group and role membership. We are limited in the number of users we can have in the 'user' role. The limit is (4000 / (39 + avg login name length)). Hope this helps. -----Original Message----- From: Martin Kalén [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 28, 2005 5:10 AM To: Slide Users Mailing List Subject: Re: Slide User Base & Oracle Support Martin, Tammy (US SSA) wrote: > I am investigating Slide and noticed that the last release 2.1 was Dec > 26, 2004. Is there another release planned or currently being worked > on? Also, I read on the site that ports for Oracle were in preparation. > Do you know when these will be ready? I don't know anything about the Slide relase plans/roadmap but I do know that Oracle support is working in 2.1 and 2.2pre (CVS HEAD). There has been some minor bugs in permission-related SQL for Oracle but this was recently fixed both on the 2.1 release branch and in CVS HEAD. However, this means that you should get a CVS snapshot build either from the stable branch or from the 2.2-preview in HEAD if you plan to deploy with Oracle RDBMS. Regards, Martin --------------------------------------------------------------------- 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]
