I may be willing to support this. I have 18 month's of Python
experience (mostly 2.4) and I have been out of work for a long time
due to illness, so a project like this may look good on my CV!
I have never been involved in an OS project before, though I am aware
of the guidelines.
At present the
On Sat, Nov 5, 2011 at 11:48 AM, Ric wrote:
> this is my proposition to have custom data inside a model field
>
> a json data field, the code is simple as this, and it works with
> lastest django release
>
The problem with something like this is that it is rarely a good idea
to stick opaque data
On 11/07/2011 12:00 PM, richard.prosser wrote:
I may be willing to support this. I have 18 month's of Python
experience (mostly 2.4) and I have been out of work for a long time
due to illness, so a project like this may look good on my CV!
I have never been involved in an OS project before, thou
you say "is rarely a good idea", and that it is the only thing true.
when, like my app, you need to handle document, real documents (like
invoice, ddt, quotations) and other stuffs, it's a good practice to
keep all in one table, separating only the things that you need to
query, and leave a non re
On Tue, Nov 8, 2011 at 5:58 AM, Ric wrote:
> you say "is rarely a good idea", and that it is the only thing true.
>
> when, like my app, you need to handle document, real documents (like
> invoice, ddt, quotations) and other stuffs, it's a good practice to
> keep all in one table, separating only
Hallöchen!
Tom Evans writes:
> On Sat, Nov 5, 2011 at 11:48 AM, Ric wrote:
>
>> this is my proposition to have custom data inside a model field
>>
>> a json data field, the code is simple as this, and it works with
>> lastest django release
>
> The problem with something like this is that it is r
