Hi, our app has a very wide table and outside of and asynchronously to the Mojo application that plucks data from the database the wide table can be widened. So for every query we check 1) the DB description of the table and 2) a list of columns descriptions (the descriptions are stored in Mongo) that define the columns that ought to be in the table (and generally are). It's a bit yucky but because the main DB is a columnar DB we can get away with it.
So schema upgrades are handled on every request to the web api :-) Allan On Friday, 26 September 2014 11:55:16 UTC-5, sri wrote: > > Wow, this thread gives a great overview of what the community currently > looks like, personally i'm (positively) surprised how strong SQL databases > are represented. So here's a bonus question, how do you manage schema > upgrades? > > -- > sebastian > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
