Re: [Dspace-tech] tcpip_socket parameter in postgresql.conf?
On Tue, Mar 25, 2008 at 12:18:05AM +, Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: I?m confused. I thought we had to have tcpip_socket = true on our postgresql.conf file in PostgreSQL 8.2/DSpace 1.4.2, but when I put it in there and try and start postmaster, it gives me an error about invalid parameter ?tcpip_socket?. Do I need this or not? This is no longer a valid configuration parameter in postgres 8.2. See http://www.postgresql.org/docs/8.2/static/runtime-config-connection.html If you set the listen_addresses parameter correctly, it should work. cheers, Jim -- James Rutherford | Hewlett-Packard Limited registered Office: Research Engineer | Cain Road, HP Labs | Bracknell, Bristol, UK | Berks +44 117 312 7066 | RG12 1HN. [EMAIL PROTECTED] | Registered No: 690597 England The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as HP CONFIDENTIAL. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Oracle and DSpace 1.5 and ILIKE
Hi -
I'm trying to install DSpace 1.5 using Oracle. It wasn't until
yesterday that I saw this in the KNOWN_BUGS file:
Oracle compatibility: this release does not support Oracle. Check for
patches or updates to this release to restore Oracle compatibility.
But nevertheless, I thought I had read that people had done successful
installs using Oracle, and I wound up also getting it installed OK, but
now I'm running into a problem in the eperson code when I click the
People link under Access Control.
Specifically, I get this exception:
java.sql.SQLException: ORA-00920: invalid relational operator
and looking through the stack trace, it appears to be coming from
org.dspace.eperson.EPerson.searchResultCount(EPerson.java:326)
where it says
TableRow row = DatabaseManager.querySingle(context,
SELECT count(*) as count FROM eperson WHERE
eperson_id = ? OR +
firstname ILIKE ? OR lastname ILIKE ? OR email
ILIKE ?,
new Object[]
{int_param,dbquery,dbquery,dbquery});
I'm pretty sure ILIKE doesn't work in Oracle, but I see this in the
1.4.2 code and I'm pretty sure I was able t create some users in that.
Does anybody have any idea about what's wrong here?
Thanks,
Rick Runyan
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Oracle and DSpace 1.5 and ILIKE
Hi,
I think it worked in 1.4.2 only if you used the default jspui interface
(it doesn't call searchResultCount). Manakin/xmlui on the other hand
does call it, so it breaks.
I altered the code to be oracle friendly:
TableRow row = DatabaseManager.querySingle(context,
SELECT count(*) as count FROM eperson WHERE eperson_id = ? OR +
lower(firstname) LIKE ? OR lower(lastname) LIKE ? OR lower(email) LIKE ?,
new Object[] {int_param,dbquery,dbquery,dbquery});
I assume that would work in postgres as well, but I haven't tested it.
You would also have to make a similar change in Group.java as well.
I haven't looked too closely at 1.5, but it works in 1.4.2.
Hope this helps.
-Greg
Rick Runyan wrote:
Hi –
I’m trying to install DSpace 1.5 using Oracle. It wasn’t until
yesterday that I saw this in the KNOWN_BUGS file:
“Oracle compatibility: this release does not support Oracle. Check for
patches or updates to this release to restore Oracle compatibility.”
But nevertheless, I thought I had read that people had done successful
installs using Oracle, and I wound up also getting it installed OK,
but now I’m running into a problem in the eperson code when I click
the “People” link under “Access Control.”
Specifically, I get this exception:
java.sql.SQLException: ORA-00920: invalid relational operator
and looking through the stack trace, it appears to be coming from
org.dspace.eperson.EPerson.searchResultCount(EPerson.java:326)
where it says
TableRow row = DatabaseManager.querySingle(context,
SELECT count(*) as count FROM eperson WHERE eperson_id = ? OR +
firstname ILIKE ? OR lastname ILIKE ? OR email ILIKE ?,
new Object[] {int_param,dbquery,dbquery,dbquery});
I’m pretty sure “ILIKE” doesn’t work in Oracle, but I see this in the
1.4.2 code and I’m pretty sure I was able t create some users in that.
Does anybody have any idea about what’s wrong here?
Thanks,
Rick Runyan
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Oracle and DSpace 1.5 and ILIKE
Cool. A fix *and* and explanation! How can you beat that?
By the way, if you're actually fixing the real code, there are more
ILIKEs in
public static EPerson[] search(Context context, String query, int
offset, int limit)
Thanks,
- Rick
-Original Message-
From: Greg McClellan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2008 4:31 PM
To: Rick Runyan
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Oracle and DSpace 1.5 and ILIKE
Hi,
I think it worked in 1.4.2 only if you used the default jspui interface
(it doesn't call searchResultCount). Manakin/xmlui on the other hand
does call it, so it breaks.
I altered the code to be oracle friendly:
TableRow row = DatabaseManager.querySingle(context,
SELECT count(*) as count FROM eperson WHERE eperson_id = ? OR +
lower(firstname) LIKE ? OR lower(lastname) LIKE ? OR lower(email) LIKE
?,
new Object[] {int_param,dbquery,dbquery,dbquery});
I assume that would work in postgres as well, but I haven't tested it.
You would also have to make a similar change in Group.java as well.
I haven't looked too closely at 1.5, but it works in 1.4.2.
Hope this helps.
-Greg
Rick Runyan wrote:
Hi -
I'm trying to install DSpace 1.5 using Oracle. It wasn't until
yesterday that I saw this in the KNOWN_BUGS file:
Oracle compatibility: this release does not support Oracle. Check for
patches or updates to this release to restore Oracle compatibility.
But nevertheless, I thought I had read that people had done successful
installs using Oracle, and I wound up also getting it installed OK,
but now I'm running into a problem in the eperson code when I click
the People link under Access Control.
Specifically, I get this exception:
java.sql.SQLException: ORA-00920: invalid relational operator
and looking through the stack trace, it appears to be coming from
org.dspace.eperson.EPerson.searchResultCount(EPerson.java:326)
where it says
TableRow row = DatabaseManager.querySingle(context,
SELECT count(*) as count FROM eperson WHERE eperson_id = ? OR +
firstname ILIKE ? OR lastname ILIKE ? OR email ILIKE ?,
new Object[] {int_param,dbquery,dbquery,dbquery});
I'm pretty sure ILIKE doesn't work in Oracle, but I see this in the
1.4.2 code and I'm pretty sure I was able t create some users in that.
Does anybody have any idea about what's wrong here?
Thanks,
Rick Runyan
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Oracle and DSpace 1.5 and ILIKE
On Tue, Mar 25, 2008 at 03:09:43PM -0400, Rick Runyan wrote:
org.dspace.eperson.EPerson.searchResultCount(EPerson.java:326)
where it says
TableRow row = DatabaseManager.querySingle(context,
SELECT count(*) as count FROM eperson WHERE
eperson_id = ? OR +
firstname ILIKE ? OR lastname ILIKE ? OR email
ILIKE ?,
new Object[]
{int_param,dbquery,dbquery,dbquery});
I'm pretty sure ILIKE doesn't work in Oracle, but I see this in the
1.4.2 code and I'm pretty sure I was able t create some users in that.
Does anybody have any idea about what's wrong here?
ILIKE is not SQL; it's a PostgreSQL extension. It's a
case-insensitive version of LIKE (which *is* SQL). The query could
probably be rewritten as:
SELECT count(*) as count FROM eperson
WHERE eperson_id = ?
OR LOWER(firstname) LIKE LOWER(?)
OR LOWER(lastname) LIKE LOWER(?)
OR LOWER(email) LIKE LOWER(?)
or as:
SELECT count(*) as count FROM eperson
WHERE eperson_id = ?
OR LOWER(firstname) LIKE ?
OR LOWER(lastname) LIKE ?
OR LOWER(email) LIKE ?
if dbquery is guaranteed to be lowercase already. Possibly these
queries would be slightly slower than what we have now, but I would
suggest that this is a place where a PGism should be sacrificed for
portability.
--
Mark H. Wood, Lead System Programmer [EMAIL PROTECTED]
Typically when a software vendor says that a product is intuitive he
means the exact opposite.
pgpv35eb2RN8Q.pgp
Description: PGP signature
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Oracle and DSpace 1.5 and ILIKE
Rick,
Thank you for the bug report. Unfortunately this patch did not make it
into the 1.5 release, which occurred earlier (before the original
email). The announcement of the release will be going out tomorrow
morning. The release has been picked up and is in the Central Maven
Repository and they have a strict policy about not allowing any
release to be revoked. The central repository plays a critical role in
maven build process, when you build DSpace with maven it will check
the repository for a specific version of a software package. Thus,
when someone downloads the DSpace release distribution (i.e. not the
source code) and runs 'mvn package' they will receive the version we
have already published into the central repository. This release of
DSpace is huge, by far the biggest release dspace has ever seen. Bugs
similar to this will likely be found in other less commonly tested
areas of DSpace in the coming few weeks. I expect there will be a
1.5.1 bug fix release soon.
This highlights how important it is for as many people as possible to
participate in the test-a-thon process, especially for those
administrators who use uncommon services such as Oracle, LDAP,
Shibboleth, or SRB. It is impossible for a developer to test these
services without access to: an Oracle database, an LDAP server, a
Shibboleth federation, or an SRB storage account. These options will
only receive as much testing as is provided by the community which
supports these options.
Until 1.5.1 is released, the work arounds available are an SVN
checkout or applying a patch. You can use the source version available
from SVN (dspace-1_5_x r2870) or apply the patch following this email.
As for a technical comment on the actual bug, there are other oracle
compatibility errors in that SQL statement beyond the ILIKE operator
in the statements that follow. The next sql statement issued after
this uses LIMIT and OFFSET, which are not supported by Oracle either.
Graham has posted a potential fix for this issue into the 1.5 branch,
however it has not been tested and may introduce pagination errors
into the UI.
Scott--
On Mar 25, 2008, at 2:09 PM, Rick Runyan wrote:
Hi –
I’m trying to install DSpace 1.5 using Oracle. It wasn’t until
yesterday that I saw this in the KNOWN_BUGS file:
“Oracle compatibility: this release does not support Oracle. Check
for patches or updates to this release to restore Oracle
compatibility.”
But nevertheless, I thought I had read that people had done
successful installs using Oracle, and I wound up also getting it
installed OK, but now I’m running into a problem in the eperson code
when I click the “People” link under “Access Control.”
Specifically, I get this exception:
java.sql.SQLException: ORA-00920: invalid relational operator
and looking through the stack trace, it appears to be coming from
org.dspace.eperson.EPerson.searchResultCount(EPerson.java:326)
where it says
TableRow row = DatabaseManager.querySingle(context,
SELECT count(*) as count FROM eperson WHERE
eperson_id = ? OR +
firstname ILIKE ? OR lastname ILIKE ? OR
email ILIKE ?,
new Object[]
{int_param,dbquery,dbquery,dbquery});
I’m pretty sure “ILIKE” doesn’t work in Oracle, but I see this in
the 1.4.2 code and I’m pretty sure I was able t create some users in
that. Does anybody have any idea about what’s wrong here?
Thanks,
Rick Runyan
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
Index: dspace-api/src/main/java/org/dspace/browse/BrowseDAOOracle.java
===
--- dspace-api/src/main/java/org/dspace/browse/BrowseDAOOracle.java
(revision 2869)
+++ dspace-api/src/main/java/org/dspace/browse/BrowseDAOOracle.java
(revision 2870)
@@ -887,7 +887,7 @@
params.add(new Integer(limit));
}
-if (offset -1)
+if (offset 0)
{
queryBuf.insert(0, SELECT * FROM ();
queryBuf.append() WHERE rnum?);
Index: dspace-api/src/main/java/org/dspace/eperson/EPerson.java
===
--- dspace-api/src/main/java/org/dspace/eperson/EPerson.java (revision
2869)
+++ dspace-api/src/main/java/org/dspace/eperson/EPerson.java (revision
2870)
@@ -253,14 +253,48 @@
throws SQLException
{
String params = %+query.toLowerCase()+%;
- String dbquery = SELECT * FROM eperson WHERE eperson_id = ? OR
+
- firstname ILIKE
[Dspace-tech] DSpace 1.5
Everyone, The DSpace community is pleased to announce the release of DSpace 1.5! This is an important release of DSpace with many new features, including a completely new theme-able Manakin user interface, SWORD integration, many new configurable options, and scalability improvements. Thanks to everyone who participated in the testing of this new release. DSpace 1.5 can be downloaded directly from SourceForge. The documentation for this release is bundled within the package and will be available shortly on the dspace.org website. http://sourceforge.net/projects/dspace/ New Features: * Maven DSpace 1.5 introduces a new Maven-based build system. Maven is a software tool from Apache that allows developers to compile and distribute software projects. Maven also enables DSpace to be more modular by arranging the software into sub-components. In addition, it makes customizations easier by giving developers the tools to maintain customizations, and provides the ability to manage new features as DSpace continues its accelerating growth rate. For more information: http://maven.apache.org/ http://www.devzuz.com/web/guest/products/resources#BBWM * Manakin Customize your repository look-and-feel with the new Manakin theme- able user interface. Manakin introduces a new modular framework, enabling an institution to customize their interface according to the specific needs of the particular repository, community, or collection. For more information: http://www.dlib.org/dlib/november07/phillips/11phillips.html Repositories currently using Manakin: http://repositories.tamu.edu/ http://repositories.tdl.org/ http://www.jobim.org/manakin/ https://www.policyarchive.org/ https://oa.doria.fi/ http://dome.mit.edu/ http://researcharchive.vuw.ac.nz/ * Light Network Interface Integrate DSpace with legacy or local systems that need to manage content in the repository through the new Light Network Interface. This interface provides a programmatic mechanism to manage content within the repository through a WebDAV or SOAP based protocol. For more information: http://wiki.dspace.org/index.php/LightweightNetworkInterface * SWORD Integrate with the new SWORD (Simple Web-service Offering Repository Deposit) protocol. Based upon the Atom Publishing Protocol, this interface allows for cross-repository deposit of new content. This protocol may enable future tools that will provide for 'one click' deposit. For more information: http://www.ukoln.ac.uk/ukoln/staff/j.allinson/or2007-deposit.pdf http://www.ukoln.ac.uk/repositories/digirep/index/SWORD_APP_Profile_1.2 * Browsing The browsing system has been completely re-implemented to provide improved scalability and configuration. The new browsing system enables administrators to easily create new browse indexes. For more information: http://www.dspace.org/index.php?option=com_contenttask=viewid=151Itemid=116 * Submissions The item submission system is now more configurable by managing the steps a user follows when submitting a new item to the repository. The new submission system allows for these steps to be rearranged, removed, and even allows for new steps to be added. For more information: https://www.ideals.uiuc.edu/bitstream/2142/207/3/OR2007-ConfigurableSubmission.ppt.pdf * Events Another under-the-hood improvement introduced in DSpace 1.5 is the event system, which improves scalability and modularity by introducing an event model to the architecture. This feature will allow future add- ons to automatically manage content in the repository based upon when an object has been added, modified, or removed from the system. For more information: http://wiki.dspace.org/index.php/EventMechanism I thank everyone who participated in testing Dspace throughout the 1.5 release process. Special thanks to Keith Gilbertson, Stuart Lewis, and Claudia Juergen for submitting many quality bug reports that were extremely helpful in polishing this release. Also, I would like to highlight the contributions of several developers: Tim Donohue for closing many bugs, Graham Triggs for his lighting fast response on browsing and database issues, and Mark Diggory for resolving build problems. Scott Phillips Research and Development Coordinator Texas Digital Library and Texas AM University Libraries [EMAIL PROTECTED] - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
