ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

repositories_helper.rb (Bug #556)

Added by rob glazer at 2011-08-03 05:29 pm. Updated at 2011-08-03 08:28 pm.

Status:Closed Start date:2011-08-03
Priority:Low Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Remote issue URL: Affected version:2.0.0

Description

Environment:
Chiliproject 2.0
Oracle 11g database
Ubuntu server

db/migrate/20100705164950_change_changes_path_length_limit.rb changes the columns to text (clob in oracle)

app/helpers/repositories_helpers.rb
line 42: changes = @changeset.changes.find(:all, :limit => 1000, :order => 'path').collect do |change|
oracle clob columns can not be in the order by unless it is cast to a varchar2 with a substr- I removed the :order => 'path' and it works properly

History

#1
Updated by Holger Just at 2011-08-03 05:39 pm

Thanks fpr your report. Unfortunately, we don't officially support Oracle as a database currently. That said, we are going to accept patches to help compatibility if those doesn't affect the functionality and performance for the other supported databases.

That brings us to your proposed fix. A limited query without an order is never correct, as the database can return an arbitrary set of elements without a specified order. That would lead no incorrect or at least unpredictable results. Because of that, we can not accept that fix as it.

Unless you find another, more correct, fix we would be forced to decline this issue.

  • Status changed from Open to Needs more information

#2
Updated by rob glazer at 2011-08-03 06:23 pm

Thanks for the reply, I will work on finding a solution to include the order by

#3
Updated by rob glazer at 2011-08-03 08:28 pm

the issue is an oracle restriction that a lob column can not be included in an order by, group by, distinct or aggregate statement.

I tested a few possible solutions but they would impact other databases.

The resolution I am testing is to change the PATH and FROM_PATH columns to VARCHAR2 on the CHANGES table, which should be large enough to hold the full path strings.

I will update the forum document on oracle installation in case anyone else encounters this issue.

Thanks.

  • Status changed from Needs more information to Closed

Also available in: Atom PDF