On Mon, Jan 31, 2011 at 5:56 PM, Jeremy Evans <[email protected]> wrote: > On Jan 31, 8:43 am, Christian MICHON <[email protected]> > wrote: >> Hi, >> >> I noticed a few things when using xml_serializer: >> - the top marker is always downcased and does not match the >> Sequel::Model class name >> - all the other markers are following exactly the table keys name, but >> sometimes you wish to export a specific key to another name without >> performing a migration of the original db tables. >> >> I wish to have control over my xml markers. Is it possible without >> having to rewrite a xmlbuilder from scratch ? >> >> Would it be possible for example to indicate that :mymarker should >> become the marker <MyMarker> when serializing out to xml ? >> >> It's especially needed for the top marker, always downcased. For the >> others, I've the option to store in another db (with the right column >> names), but it's a lot of data duplication... > > I'd consider a patch that wasn't too invasive and came with specs. > > Jeremy > > -- > You received this message because you are subscribed to the Google Groups > "sequel-talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sequel-talk?hl=en. > >
I'll need to have a deeper look at the code then. It means that right now what I observe is normal/expected... Thx Christian -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
