On 6-Jun-08, at 12:04 PM, Renato Golin wrote:
Arek Kasprzyk wrote:
Hi Renato,
in order to actually run it the transform the source and target
schemas need to be on the same server (hence platform) in any case
Hi Arek,
That won't work with UniProt at all. It's impossible for me to add
the whole bunch of biomart tables to our production database,
especially because I want to get the information from the read-only
database.
I understand that it may be easier to use Oracle on both sides
(although, as you have your own model, it shouldn't be a problem to
export to any flavour of SQL the builder supports) but requiring it
to be in the same schema is just silly.
sorry you misunderstood me :) of course it does not have to be in the
same schema. (it could be) but normally it ends up in a separate schema.
however the SQL statements there which do the transform and being
executed ( eg "CREATE TABLE mart_shema.new_table as SELECT FROM
source_schema.table_a, source_schema.table_b ... etc")
assume this is run on the same platform
did I understand it correctly?
a.
Besides, I think that MySQL would do a *much* better job for BioMart
since it won't have all the wasted effort on mapping constraints (I
was planning to use MyIsam) because it's supposed to be a flattened
database after all (isn't it?).
cheers,
--renato
