Cannot view previously saved static datasets

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Go to the DHOxSS project on Dev, and look at the datasets for the Club 
membership database (Mark, you should have access to this)
2. Try to view the two static datasets
3.

What is the expected output? What do you see instead?
I don't know whether this is related to issue 585, or if it's a different 
problem, but trying to view either of those datasets produces what I think is 
the longest ORDS error message I've ever seen. The non-static one seems fine.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by meriel.p...@gmail.com on 17 Dec 2014 at 6:59

[GoogleCodeExporter]

Upping to critical

Original comment by jajwil...@gmail.com on 5 Jan 2015 at 11:20

• Added labels: Priority-Critical
• Removed labels: Priority-High

[GoogleCodeExporter]

Original comment by jajwil...@gmail.com on 7 Jan 2015 at 4:17

• Added labels: Milestone-1.0.7

[GoogleCodeExporter]

As I suspected this was a result of my changes to fix the sorting.  Problem is 
now fixed!

Original comment by marxjohn...@gmail.com on 8 Jan 2015 at 10:14

• Changed state: Fixed

[GoogleCodeExporter]

I'm having this problem again on the new Staging version (v. 1.0.7~ox.0 - 
4013). Have a look at the dataset list for London Victorian Gentlemen's Clubs > 
Main clubs database. The two dynamic ones work fine; the static one produces an 
error message. (Bizarrely, all three are fine when viewed via the ORDS public 
project search.)

Original comment by meriel.p...@gmail.com on 19 Jan 2015 at 6:40

• Changed state: Started

[GoogleCodeExporter]

Dave,
Looking at the error below, this seems to be a similar problem to those that I 
sent you when updating the Selenium tests - I guess that this page isn't 
covered by the tests.
If you're otherwise engaged I'm happy to implement the fix, if it's quicker for 
you to explain what needs to be done that to do it yourself.

An error occurred at line: 31 in the generated java file
Only a type can be imported. 
uk.ac.ox.oucs.ords.ordsProjectNode.utilities.database.PostgresDBUtils resolves 
to a package

An error occurred at line: 63 in the jsp file: /queryViewer.jsp
PostgresDBUtils cannot be resolved to a type
60:             Project project = 
DBGateway.getProject(database.getDatabaseProjectId());
61:             String cleanProjectName = 
StringEscapeUtils.escapeHtml4(project.getName());
62:             OrdsPhysicalDatabase opd = 
DBGatewayProjectNode.getPhysicalDatabaseByPhysicalDatabaseId(Integer.parseInt(cl
eanPhysicalId));
63:             PostgresDBUtils dbUtils = new 
PostgresDBUtils(DBGateway.getDbServerByProjectId(cleanProjectId), 
opd.getDbConsumedName());
64:             Collection<DataRow> tableList = 
dbUtils.getTableListForMainDatabase(cleanPhysicalId);
65:             Collection<DataRow> cols;
66:             cols = (Collection<DataRow>) 
dbUtils.getColumnNamesForTable(cleanTableName).rows.values();

Original comment by marxjohn...@gmail.com on 21 Jan 2015 at 10:29

[GoogleCodeExporter]

Original comment by thest...@gmail.com on 22 Jan 2015 at 1:29

[GoogleCodeExporter]

This should now be fixed. I don't have access to the DHOxSS project - if the 
problem persists then please add me to the project and I'll take another look

Original comment by thest...@gmail.com on 22 Jan 2015 at 1:44

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by thest...@gmail.com on 22 Jan 2015 at 1:59

[GoogleCodeExporter]

I'm still having the same problem. 

Dave, I've just tried to add you to the project as a member, but ORDS said you 
weren't registered. (I've sent you an invitation - is that functionality 
working now?)

Original comment by meriel.p...@gmail.com on 23 Jan 2015 at 2:51

[GoogleCodeExporter]

Original comment by meriel.p...@gmail.com on 23 Jan 2015 at 3:03

• Changed state: Started

[GoogleCodeExporter]

I've just realized that the database I'm having problems with is on Staging, 
not Dev, so presumably the problem is just that Staging has the old version of 
the code on it. Seems fine on Dev, so I'll mark this as fixed again. Sorry for 
the confusion!

Original comment by meriel.p...@gmail.com on 23 Jan 2015 at 6:00

• Changed state: Fixed