> From: Matt Cottingham
>Sent: Wednesday, December 19, 2012 3:35 PM
> 
> FROM: Matt Cottingham
> TO: dkuhl...@rexx.com 
> Wednesday, December 19, 2012 3:36 PM
> 
> Hi Dave,
> 
> Thanks for generateDS - it's already saved me lots of time!
> 

Matt -

Great.  I'm gratified to hear that.

> I've used gends_run_gen_django.py to create django models from an
> XSD. My question is - do you have a recommended way of populating
> these models from an XML file?
> 
> I previously used the 'parse' method on a module generated by
> generateDS to great effect - so I'm hoping I can modify this to
> instantiate django models directly as part of a bulk load process.
> 

It sounds to me that you are suggesting that generateDS.py should be
able to (optionally) generate in each data representation class the
methods buildDjango, buildDjangoAttributes, and buildDjangoChildren,
or perhaps better yet, exportDjango, exportDjangoAttributes, and
exportDjangoChildren.

That's a reasonably ambitious enhancement.  I suspect that I
wouldn't be able to do anything soon.  Actually, I've moved on from
Django (not because Django isn't a great platform, but because I'm
now interested in Erlang web frameworks), so I would not even be
"scratching my own itch".

Also, I'd like to make it more general purpose so that it covered a
broader class of use cases.

Let me think about it.  But, you shouldn't expect anything soon.

You might consider using the --member-specs command line option, and
then looking at the information it generates (member_data_items_ in
each data representation class).  Perhaps that might enable you to
write something generic enough to be able to be used in every class.

Here is an example of what that specification looks like (generated
with --member-spec=list):

class personType(GeneratedsSuper):
          member_data_items_ = [
                MemberSpec_('vegetable', 'xs:string', 0),
                MemberSpec_('fruit', 'xs:string', 0),
                MemberSpec_('ratio', 'xs:float', 0),
                MemberSpec_('id', 'xs:integer', 0),
                MemberSpec_('value', 'xs:string', 0),
                MemberSpec_('name', 'xs:string', 0),
                MemberSpec_('interest', 'xs:string', 1),
                MemberSpec_('category', 'xs:integer', 0),
                MemberSpec_('agent', 'agentType', 1),
                MemberSpec_('promoter', 'boosterType', 1),
                MemberSpec_('description', 'xs:string', 0),
                MemberSpec_('range_', ['RangeType', 'xs:integer'], 0),
                ]

Would that be enough information to enable you to write a generic
function that could be applied to any generated class so as to store
the data in a Django model/database?

Hope this is of at least a little bit of help.

And, if you do implement something that you think might be useful to
others with a similar need, please let me know.

- Dave


--


Dave Kuhlman
http://www.rexx.com/~dkuhlman

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
generateds-users mailing list
generateds-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/generateds-users

Reply via email to