Hi, in my previous message, I made a misleading and incorrect reference to
the list which should properly be referred to as the changelog list; for
posterity's sake, here's a link to the correct mail list:

https://lists.sourceforge.net/lists/listinfo/dspace-changelog


I'm adding myself now, following my own advice :-) and will endeavor to be
a better DSpace community member by testing patches that seem like they
might impact Oracle compatibility.

--
HARDY POTTINGER <pottinge...@umsystem.edu>
University of Missouri Library Systems
http://lso.umsystem.edu/~pottingerhj/
"No matter how far down the wrong road you've gone,
turn back." --Turkish proverb






On 5/2/11 12:33 PM, "Pottinger, Hardy J." <pottinge...@umsystem.edu> wrote:

>Hi, Richard, I think what needs to happen is someone from our community of
>Oracle installations needs to commit an Oracle-backed installation to the
>next Testathon, to catch items like this. I am also going to try to do
>more testing along the way. I think what we need to do as a community is
>to be especially vigilant for patches that touch the classes that interact
>with the database in any way, as this area of DSpace is particularly
>important to our use of DSpace.
>
>I'd like to reach out to the more-experienced developers on this list: is
>there a good way, besides "paying more attention" to follow the commits
>and watch out for changes to the database classes? Do I need to just join
>the commit mail list and set up a a filter in my mail client? Or is there
>some better way to keep on top of these things?
>
>Also, Richard, this a very minor detail, but I am the reporter for DS-841,
>Peter was kind enough to add a comment on my behalf, when I could not
>figure out how to add one (I was home sick with a case of the flu on that
>day, and I appreciate Peter's willingness to do that for me).
>--
>HARDY POTTINGER <pottinge...@umsystem.edu>
>University of Missouri Library Systems
>http://lso.umsystem.edu/~pottingerhj/
>"No matter how far down the wrong road you've gone,
>turn back." --Turkish proverb
>
>
>
>
>
>
>On 5/2/11 8:59 AM, "Jizba, Richard" <richardji...@creighton.edu> wrote:
>
>> 
>>We have encountered the problem reported previously by Peter Dietz:
>>http://dspace.2283337.n4.nabble.com/DuraSpace-JIRA-Created-DS-841-Illegal
>>A
>>rgumentException-No-such-column-rnum-error-in-DSpace-1-7-x-XML-td3381504.
>>h
>>tml  
>>('IllegalArgumentException: No such column rnum' error in DSpace 1.7.x
>>XMLUI admin eperson (with Oracle backend))
>> 
>>Any release date for 1.7.2?
>> 
>>Also, in the older "Reference Theme", the simple solr statistics do not
>>display.
>>Look at: http://hdl.handle.net/10504/90
>> 
>>Any explanation for why the Oracle side has been so buggy with this
>>version? This isn't helping my cause locally as a promoter of dspace. I
>>am not a programmer, but I would be happy to beta-test the next version
>>to catch any Oracle issues.
>> 
>>Richard Jizba
>>Health Sciences Library
>>Creighton University
>>(402) 280-5142
>>rji...@creighton.ed
>> 
>
>
>--------------------------------------------------------------------------
>----
>WhatsUp Gold - Download Free Network Management Software
>The most intuitive, comprehensive, and cost-effective network
>management toolset available today.  Delivers lowest initial
>acquisition cost and overall TCO of any competing solution.
>http://p.sf.net/sfu/whatsupgold-sd
>_______________________________________________
>DSpace-tech mailing list
>DSpace-tech@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/dspace-tech


------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to