You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by Matt Franklin <m....@gmail.com> on 2013/02/12 23:42:44 UTC
Deprecating initial-data.sql
During the MongoDB support work, I created a DataImporter that
deserializes a JSON file and uses the Repositories to save initial
bootstrap data into the database. I have just finished making this
model compatible with JPA. What would everyone think about making
this the primary supported method for the demo binary data?
IMO, JSON is much easier to maintain than a SQL file and the current
version is actually a serialization of the objects created by
initial-data.sql (with some tweaks). This method also should work
regardless of the underlying repository type, which means we only need
to maintain one data file.
Re: Deprecating initial-data.sql
Posted by Jasha Joachimsthal <ja...@apache.org>.
Thanks Matt, this is something we've been needing for a long time.
+∞ (+1 in case infinity is not a valid option)
On 12 February 2013 23:42, Matt Franklin <m....@gmail.com> wrote:
> During the MongoDB support work, I created a DataImporter that
> deserializes a JSON file and uses the Repositories to save initial
> bootstrap data into the database. I have just finished making this
> model compatible with JPA. What would everyone think about making
> this the primary supported method for the demo binary data?
>
> IMO, JSON is much easier to maintain than a SQL file and the current
> version is actually a serialization of the objects created by
> initial-data.sql (with some tweaks). This method also should work
> regardless of the underlying repository type, which means we only need
> to maintain one data file.
>
Re: Deprecating initial-data.sql
Posted by Ate Douma <at...@douma.nu>.
Cool and thanks Matt!
I'm very much +1 on this one.
On 02/12/2013 11:42 PM, Matt Franklin wrote:
> During the MongoDB support work, I created a DataImporter that
> deserializes a JSON file and uses the Repositories to save initial
> bootstrap data into the database. I have just finished making this
> model compatible with JPA. What would everyone think about making
> this the primary supported method for the demo binary data?
>
> IMO, JSON is much easier to maintain than a SQL file and the current
> version is actually a serialization of the objects created by
> initial-data.sql (with some tweaks). This method also should work
> regardless of the underlying repository type, which means we only need
> to maintain one data file.
>
Re: Deprecating initial-data.sql
Posted by Matt Franklin <m....@gmail.com>.
Sounds good. I will start working this now. It will have some impact
on the spring config organization, such as the rave-jpa jar will no
longer have a persistence context.
On Wed, Feb 13, 2013 at 8:41 AM, Marlon Pierce <ma...@iu.edu> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> +1 I'd like to pile on.
>
>
> Marlon
>
>
> On 2/12/13 5:42 PM, Matt Franklin wrote:
>> During the MongoDB support work, I created a DataImporter that
>> deserializes a JSON file and uses the Repositories to save initial
>> bootstrap data into the database. I have just finished making
>> this model compatible with JPA. What would everyone think about
>> making this the primary supported method for the demo binary data?
>>
>> IMO, JSON is much easier to maintain than a SQL file and the
>> current version is actually a serialization of the objects created
>> by initial-data.sql (with some tweaks). This method also should
>> work regardless of the underlying repository type, which means we
>> only need to maintain one data file.
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJRG5giAAoJEOEgD2XReDo5p+EH/1fuVJQN22BVwdElSC9YB4kg
> V1ro4aaAGqHzapwUg80rSfXHkl5F+D69yfp2xBhMXJzWc04F1Osr+TaKb9Tsyd2w
> aoMIv+RFlXWubOYtjgZz6vuQLLF/vhih3787fddyWH/YUYP4Mdr1aXLpCnpqXdpV
> 3SI31qjNsRhSQeYjvG1jgAa+bvfmD/cilZlomLW5gmC6tB6HTQodVk9H+63W6amX
> aAnx6aVQ1obkt10tsuIlkf7jNswtMNdD17EgdqZ403UrdXFcTsNIETVn9EMRJFlQ
> ncgca7j1vWykNdOG1uxDd8v7fazjQQdeH8Qmo0Ei9W9ycz6Cuqd7ZWVcq+EPf9Y=
> =wuFA
> -----END PGP SIGNATURE-----
Re: Deprecating initial-data.sql
Posted by Marlon Pierce <ma...@iu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
+1 I'd like to pile on.
Marlon
On 2/12/13 5:42 PM, Matt Franklin wrote:
> During the MongoDB support work, I created a DataImporter that
> deserializes a JSON file and uses the Repositories to save initial
> bootstrap data into the database. I have just finished making
> this model compatible with JPA. What would everyone think about
> making this the primary supported method for the demo binary data?
>
> IMO, JSON is much easier to maintain than a SQL file and the
> current version is actually a serialization of the objects created
> by initial-data.sql (with some tweaks). This method also should
> work regardless of the underlying repository type, which means we
> only need to maintain one data file.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRG5giAAoJEOEgD2XReDo5p+EH/1fuVJQN22BVwdElSC9YB4kg
V1ro4aaAGqHzapwUg80rSfXHkl5F+D69yfp2xBhMXJzWc04F1Osr+TaKb9Tsyd2w
aoMIv+RFlXWubOYtjgZz6vuQLLF/vhih3787fddyWH/YUYP4Mdr1aXLpCnpqXdpV
3SI31qjNsRhSQeYjvG1jgAa+bvfmD/cilZlomLW5gmC6tB6HTQodVk9H+63W6amX
aAnx6aVQ1obkt10tsuIlkf7jNswtMNdD17EgdqZ403UrdXFcTsNIETVn9EMRJFlQ
ncgca7j1vWykNdOG1uxDd8v7fazjQQdeH8Qmo0Ei9W9ycz6Cuqd7ZWVcq+EPf9Y=
=wuFA
-----END PGP SIGNATURE-----
Re: Deprecating initial-data.sql
Posted by Chris Geer <ch...@cxtsoftware.com>.
On Tue, Feb 12, 2013 at 3:46 PM, Noe-Payne, Erin A. <er...@mitre.org>wrote:
> Love it. +1
>
> On 2/12/13 5:42 PM, "Matt Franklin" <m....@gmail.com> wrote:
>
> >During the MongoDB support work, I created a DataImporter that
> >deserializes a JSON file and uses the Repositories to save initial
> >bootstrap data into the database. I have just finished making this
> >model compatible with JPA. What would everyone think about making
> >this the primary supported method for the demo binary data?
> >
> >IMO, JSON is much easier to maintain than a SQL file and the current
> >version is actually a serialization of the objects created by
> >initial-data.sql (with some tweaks). This method also should work
> >regardless of the underlying repository type, which means we only need
> >to maintain one data file.
>
+1
Re: Deprecating initial-data.sql
Posted by "Noe-Payne, Erin A." <er...@mitre.org>.
Love it. +1
On 2/12/13 5:42 PM, "Matt Franklin" <m....@gmail.com> wrote:
>During the MongoDB support work, I created a DataImporter that
>deserializes a JSON file and uses the Repositories to save initial
>bootstrap data into the database. I have just finished making this
>model compatible with JPA. What would everyone think about making
>this the primary supported method for the demo binary data?
>
>IMO, JSON is much easier to maintain than a SQL file and the current
>version is actually a serialization of the objects created by
>initial-data.sql (with some tweaks). This method also should work
>regardless of the underlying repository type, which means we only need
>to maintain one data file.