Re: GSoC: Data importation class

Or let's circumvent the whole problem by stopping this garbage at the gates! On Mar 25, 11:34 pm, Richard Laager wrote: > This might be a bit off-topic for this thread, but legacy data is why I > wish frameworks supported some concept of warnings in their validation > code. >

Re: GSoC: Data importation class

> On 25/03/10 17:47, subs...@gmail.com wrote: > > >> The last bit sounds a bit nebulous. You could optimise it by not > >> including any empty files, or be a bit more specific about what the > >> empty files are meant to represent. :) > > > startapp, startproject, et al. > > I see where you're

Re: GSoC: Data importation class

On Thu, 2010-03-25 at 11:34 -0500, Malcolm Tredinnick wrote: > That's not a correct statement, since Django models can often be used to > proscribe conditions on new data that is created via the web app, yet > those conditions might not be required for the universal set of data > that already

Re: GSoC: Data importation class

I feel the need to wade in here, since this is vaguely my area. On 25/03/10 17:47, subs...@gmail.com wrote: The last bit sounds a bit nebulous. You could optimise it by not including any empty files, or be a bit more specific about what the empty files are meant to represent. :)

Re: GSoC: Data importation class

> > Adding system administration functionality to Django, which is what this > > monitoring is, feels like the wrong approach. I see here you probably meant its appropriate elsewhere but not in django. Gotcha. Thought I'd try anyhow. -- You received this message because you are subscribed to

Re: GSoC: Data importation class

On Mar 25, 12:34 pm, Malcolm Tredinnick wrote: > Hi, > > I see a few problems here. The gist of what follows is that it seems a > bit abstract and as one tries to nail down the specifics it either > devolves to a more-or-less already solved problem that doesn't require >

Re: GSoC: Data importation class

Hi, I see a few problems here. The gist of what follows is that it seems a bit abstract and as one tries to nail down the specifics it either devolves to a more-or-less already solved problem that doesn't require Django core changes, or a problem that is so unconstrained as to not be solvable by

GSoC: Data importation class

If we could visualize the entirety of data within django-projects, we would probably see that this 'data economy' is growing exponentially year-over-year. However, I know of no guided way to actually get this data into a project that's been converted to Django. There are two methods I generally