In Oracle, you can assign a default tablespace to an owner (schema). We are moving all our spatial databases to PostGIS where a schema cannot have a default tablespace. Instead you have to specify the tablespace to use with the create table syntax.
With FME desktop, how can I specify what tablespace I want all these cloned tables to go into without first somehow creating empty tables myself and then appending to them?
Best answer by hallkbrdz
The answer (for all tables per worksheet) is to use the writer parameter "SQL to run before write" and then simply set the tablespace that will be used by default:
SET default_tablespace = xyz
Not ideal, but good enough for now.
Bryan
+18Tia,
In Oracle we generally use one tablespace for each schema that holds a large number of tables, so yes. This helps keep a tablespace to a resonable size, and on Oracle it allowed us to backup/restore by tablespace if we wanted to clone data that way.
For PostGIS, I was just planning on mimicking the same layout.
Bryan
+29Table Qualifier is the field you are looking for.
Splitted:
Table Name: table_a
Table Qualifier: schema_a
Or one field:
Table Name: schema_a.table_a
Table Qualifier: {leave emtpy}
Because the FeatureReader sets the fme_feature_type to schema_a.table_a the none splitted variant can come in handy.
Table Qualifier is the field you are looking for.
+18Tia,
In Oracle we generally use one tablespace for each schema that holds a large number of tables, so yes. This helps keep a tablespace to a resonable size, and on Oracle it allowed us to backup/restore by tablespace if we wanted to clone data that way.
For PostGIS, I was just planning on mimicking the same layout.
Bryan
The answer (for all tables per worksheet) is to use the writer parameter "SQL to run before write" and then simply set the tablespace that will be used by default:
SET default_tablespace = xyz
Not ideal, but good enough for now.
Bryan
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
