A new topic, 'Organization of production and testing environments', has been
made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=645.new#new
The text of the topic is shown below:
Hello, Nathan!
Could you help me with some advice?
I have successfully set up liquibase on MySQL with structure similar to Oracle
tutorial article.
The problem is that I'm working now on the script that would import data from
old Paradox database to the new mysql one.
So the data is quite big, maybe it's about 100M sql dump file. Is that a best
practice to store production data in repository?
I don't like this idea because:
1) it's very big and it would be a pain for other programmers with bad internet
connection to get this data
2) the repository become +100M bigger
3) leaking users information
But
1) some modules in our systems need various data with large amounts of time
(for example, reports)
2) it's hard to test system without real data
3) generating test data can become a challenge
How do you solve these problems?
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The Liquibase Community Forum Team.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user
