Database: Oracle GeoServer: trunk module: app-schema I notice that during loading of my mapping files, the <sourcetype> is type sensitive. eg
If I have a table in oracle call "mytable" and in my mapping file <sourcetype>mytable</mytable>, it would load up fine but the moment a request is made it converts mytable to MYTABLE (since oracle default is upper case). My question here is, what should the behaviour be like? should geoserver handle mapping files case insensitively or sensitively? Right now, the only way to use oracle database is to have everything in upper case including database table name. using "lower_cases" in the table name would cause an table or view not found error. -- View this message in context: http://old.nabble.com/GeoServer-Case-sensitive-tp29113779p29113779.html Sent from the GeoServer - Dev mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
