Hello,
I just downloaded geonetwork2 and put it into my tomcat server; to my mind a big improvement against the first genetwork version. However, like in the first version the table names are “hard-wired” in the code. When using database systems like ORACLE containing a larger number of tables this might be (in my case it is) a problem because other systems may use the same table names. Because of this I changed the code slightly to be able to change the table names easily by modifying some entries in the org.fao.geonet.constants.Geonet class (by simply adding a new class “Tables”):
public class Tables
{
public static final String TAB_CATEGORIES = “GEONET_CATEGORIES”;
public static final String TAB_DATALOCATION = “GEONET_DATALOCATION”;
public static final String TAB_GROUPS = “GEONET_GROUPS”;
public static final String TAB_HELP = “GEONET_HELP”;
public static final String TAB_METADATA = “GEONET_METADATA”;
public static final String TAB_METADATACATS = “GEONET_METADATACATS”;
public static final String TAB_OPERATIONALLOWED= “GEONET_OPERATIONALLOWED”;
public static final String TAB_OPERATIONS = “GEONET_OPERATIONS”;
public static final String TAB_USERGROUPS = “GEONET_USERGROUPS”;
public static final String TAB_USERS = “GEONET_USERS”;
}
In the remaining code I changed all fixed table names to variable Strings. Is there any interest to include this option in forthcoming releases (I could deliver a list of necessary changes)?
Secondly as a short question: are featured maps are already supported in the new release?
Best regards
Ralf Kunkel
You should not have such problems simply because every oracle user has his
own schema. Since geonetwork's table names are not qualified (i.e. without
the schema) oracle should use the user's one. In FAO, the dbms used is oracle
and there have been no name conflicts.
I would like to know if other users have the same problem.
Cheers,
Andrea
Hello,
I just downloaded geonetwork2 and put it into my tomcat server; to my mind a
big improvement against the first genetwork version. However, like in the
first version the table names are "hard-wired" in the code. When using
database systems like ORACLE containing a larger number of tables this might
be (in my case it is) a problem because other systems may use the same table
names. Because of this I changed the code slightly to be able to change the
table names easily by modifying some entries in the
org.fao.geonet.constants.Geonet class (by simply adding a new class
"Tables"):
public class Tables
{
public static final String TAB_CATEGORIES = "GEONET_CATEGORIES";
public static final String TAB_DATALOCATION = "GEONET_DATALOCATION";
public static final String TAB_GROUPS = "GEONET_GROUPS";
public static final String TAB_HELP = "GEONET_HELP";
public static final String TAB_METADATA = "GEONET_METADATA";
public static final String TAB_METADATACATS = "GEONET_METADATACATS";
public static final String TAB_OPERATIONALLOWED=
"GEONET_OPERATIONALLOWED";
public static final String TAB_OPERATIONS = "GEONET_OPERATIONS";
public static final String TAB_USERGROUPS = "GEONET_USERGROUPS";
public static final String TAB_USERS = "GEONET_USERS";
}
In the remaining code I changed all fixed table names to variable Strings.
Is there any interest to include this option in forthcoming releases (I
could deliver a list of necessary changes)?
Secondly as a short question: are featured maps are already supported in the
new release?
Best regards
Ralf Kunkel