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

From: Michael Bergens (JIRA) ("Michael)
Date: Mon Jan 21 2008 - 11:18:34 EST

  • Next message: Michael Bergens (JIRA): "[JIRA] Created: (CAY-972) Need ability to set next available generated primary key value"

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

    Michael Bergens commented on CAY-968:
    -------------------------------------

    DBUnit seems ok for *small* sets of data; but sometimes our test sets are quite beefy: hundreds of tables with many megs of info, DBUnit does not seems to scale well into those quantities.

    Derby, HSQL, H2 are binary form therefore not versionable.

    Ideal solution that adresses versioning, scales quite well is selective import/export into table-by-table xmls with exclusion of audit trail and transaction tables that are always huge and mostly useless for testing.

    > 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.
    



    This archive was generated by hypermail 2.0.0 : Mon Jan 21 2008 - 11:19:08 EST