You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by "Ari Maniatis (JIRA)" <de...@cayenne.apache.org> on 2008/01/21 07:42:33 UTC

[JIRA] Commented: (CAY-968) Portable Data with Cayenne - database load/unload feature

    [ https://issues.apache.org/cayenne/browse/CAY-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12692#action_12692 ] 

Ari Maniatis commented on CAY-968:
----------------------------------

If you are using this for testing (and maybe even if you are not), then this is one approach:

http://www.dbunit.org/

> Portable Data with Cayenne - database load/unload feature
> ---------------------------------------------------------
>
>                 Key: CAY-968
>                 URL: https://issues.apache.org/cayenne/browse/CAY-968
>             Project: Cayenne
>          Issue Type: New Feature
>          Components: Cayenne Core Library
>    Affects Versions: UNDEFINED FUTURE
>            Reporter: Michael Bergens
>            Assignee: Andrus Adamchik
>            Priority: Minor
>
> Here's a dream: I run an ant target or a set of API calls with proper configuration against a database configured with Cayenne, it gives me a set of files or just one file, possibly some compressed archive format such as zip which contain all I need to recreate the same data under the same DBMS or a different one. So whenever needed, I can send this file or files to a colleague who would run a reverse ant target (or a set of API calls) and have the same database ready for use in the DBMS of his choice.
> Cayenne has plenty of good stuff which would make this possible and my team is currently implementing subset of this functionality tailored to our specifics: it requires some manual effort on the part of indicating the sequence in which the tables should be loaded, manual adjustment of primary key generation info after loading a table etc. Would be good to have this implemented in a core or an optional extension. The portable format should be versionable plain text such as XML or JSON - that would allow me to to use the VCS to keep my test data, demo data etc, properly versioned.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.