|
| Re: CDO export/import of data [message #1018375 is a reply to message #1018295] |
Wed, 13 March 2013 18:06   |
|
Am 13.03.2013 16:17, schrieb Andrew Whelan:
> Greetings,
>
> I am just looking for affirmation on what I suspect is the extent of the CDO import/export functionality that is
> currently available to clients.
>
> Class org.eclipse.emf.cdo.server.CDOServerExporter.XML has functionality to export a full repository to an XML file.
Yes.
> Class org.eclipse.emf.cdo.server.CDOServerImporter.XML has functionality to import a full repository from an XML file
> to a new repository.
Yes.
> There is currently no functionality that will let you export a few records (maybe filtered on timestamp and branch) to
> an XML file and then import those records into a repository that already exists and has data in it.
>
> Does this sound correct?
Yes. This export/import is really more a backup/restore kind of thing. What you're talking about can be accomplished on
the CDO client side with code that works with pure EMF APIs. And there is the new (client side) CDO transfer framework
that also backs the drag and drop from and into the workspace or the external file system.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
| Re: CDO export/import of data [message #1021223 is a reply to message #1020730] |
Tue, 19 March 2013 17:21 |
|
Am 18.03.2013 21:20, schrieb Andrew Whelan:
> Eike,
> I'm just looking for some verification here. It doesn't look like CDOServerImporter.XML/CDOServerExporter.XML works
> with qualifiedNames=true does it?
I'm not exactly sure what"works with" means. CDOServerExporter.XML.exportRevision(XMLOutput, CDORevision) outputs a
fully qualified class:
out.attribute(REVISION_CLASS, new CDOClassifierRef(rev.getEClass()).getURI());
CDOServerImporter imports into a repository that you have to instantiate yourself, not activate it and then pass it into
the constructor of CDOServerImporter. So qualifiedNames is set to whatever you created this repository with.
Does that help?
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
> With MySQL I end up with Table 'nighthawk.cdoresourcefolder' doesn't exist. "nighthawk" is the schema name and there
> is no cdoresourcefolder when Table qualifiedNames=true, but there is with qualifiedNames=false.
|
|
|
|
|
| Re: CDO export/import of data [message #1021787 is a reply to message #1021344] |
Wed, 20 March 2013 17:19 |
|
Am 19.03.2013 23:37, schrieb Andrew Whelan:
> Forget the last response. I was confusing concepts, I'm tired and I need to go home. The "nighthawk" we see in the
> exception is the name of the schema I created for the MySQL database. I am also using a model named nighthawk but that
> isn't your concern.
>
> If I run the CDOServer with qualifiedNames=false and use the Library model, I can import and export just fine. The
> database schema that is generated has a cdoresourcefolder table.
>
> If I have qualifiedNames=true and use the Library model there is no cdoresourcefolder generated.
>
> If I try to run the export I get the exception I reported. I can't use qualifiedNames=false with my model because it
> has duplicate element names that are distinguished by qualified names. Sorry about the confusion in the last response.
>
> Does that make sense?
Have you tried it with H2 to get an indication whether the problem depends on the DB type?
qualifiedNames==true must work. If it doesn't it may be a bug and you should report it.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
Powered by
FUDForum. Page generated in 0.02208 seconds
Search
Help
Register
Login
Home
