[Building Sakai] Sakai 2.7 with mysql 5.5 and SAKAI_PERSON_T?

John Bush john.bush at rsmart.com
Thu May 19 16:33:41 PDT 2011


I think hibernate takes care of that, I can test this tomorrow:

if the queries are something like:

select * from SAKAI_PERSON_T where FAVOURITE_BOOKS like '%KORAN%'

those work just fine

On Thu, May 19, 2011 at 3:45 PM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> Ok thanks for the input here.
>
> I've filed this as https://jira.sakaiproject.org/browse/SAK-20598
>
> One issue though is that if the field is a CLOB in Oracle, then the current
> free text searching that takes place on those fields will not work. Unless
> hibernate has a way of automatically dealing with this.
>
> AFAIK the SQL needs to be to_char(clob_field) so that it can be retrieved
> as a string again. Anyone know anything about this?
>
> thanks,
> Steve
>
>
>
> On 20/05/2011, at 1:23 AM, Earle Nietzel wrote:
>
> I believe the type on those needs to be set to text for it to work
> appropriately.
>
> i.e.
> This is wrong:
> <property name="notes" column="NOTES" type="string" length="75000" />
>
> This is correct:
> <property name="notes" column="NOTES" type="text" length="75000" />
>
> As John commented, the number 75000 was just a number I came up with.
> I think any number should work within the range 1 - Integer.MAX_VALUE.
>
> Earle
>
>
> On Wed, May 18, 2011 at 10:11 PM, John Bush <john.bush at rsmart.com> wrote:
>
> increasing the length while using type of string breaks oracle, increasing
>
> length while using type of text works universally.  current settings break
>
> mysql when using the innodb5 dialect. im suggesting type=text length=75000
>
> or more, which requires oracle start using clobs but works for mysql all
>
> dialects, db2 , and oracle
>
>
> Not sent with my iphone.
>
>
> On May 18, 2011 4:33 PM, "Steve Swinsburg" <steve.swinsburg at gmail.com>
>
> wrote:
>
>
> Hi John,
>
>
> This does not work for Oracle, the tries to create everything like longs,
>
> hibernate generates this...
>
>
> Which part doesn't work? The current settings (4000) or the new ones
>
> (75000)?
>
>
> The HBM for SAKAI_PERSON_T already specifies both type and length:
>
>
> https://source.sakaiproject.org/svn//common/trunk/impl/src/java/org/sakaiproject/component/common/edu/person/SakaiPersonImpl.hbm.xml
>
> Currently, for the large fields, it is something like:
>
>
> <property name="notes" column="NOTES" type="string" length="4000" />
>
>
> So can you confirm that increasing the length to something like 75000 makes
>
> Hibernate behave on both Oracle and MySQL?
>
> thanks,
>
> Steve
>
>
>
> On 19/05/2011, at 6:40 AM, John Bush wrote:
>
>
> This does not work for Oracle, the tries to create everything like longs,
>
> hibernate generates this...
>
>
> <sakai_person.patch>
>
>
> _______________________________________________
>
> sakai-dev mailing list
>
> sakai-dev at collab.sakaiproject.org
>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
>
> with a subject of "unsubscribe"
>
>
>
>


-- 
John Bush
602-490-0470
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110519/bbf5ce85/attachment.html 


More information about the sakai-dev mailing list