On Sat, 2009-01-31 at 13:13 -0800, Vinay Sajip wrote:
>
>
> On Jan 30, 1:36 am, Malcolm Tredinnick
> wrote:
> > On Wed, 2009-01-28 at 23:21 -0800, Vinay Sajip wrote:
> >
> > [...]
> >
> > > I was hoping there was another way. Of course subclassing's not hard
> > > to do, but it means doing it f
On Jan 30, 1:36 am, Malcolm Tredinnick
wrote:
> On Wed, 2009-01-28 at 23:21 -0800, Vinay Sajip wrote:
>
> [...]
>
> > I was hoping there was another way. Of course subclassing's not hard
> > to do, but it means doing it for every field class. I was looking at
> > moving an application over from
On Wed, 2009-01-28 at 23:21 -0800, Vinay Sajip wrote:
[...]
> I was hoping there was another way. Of course subclassing's not hard
> to do, but it means doing it for every field class. I was looking at
> moving an application over from SQLAlchemy, which offers this feature
> both for models and fi
On Jan 29, 12:35 am, Malcolm Tredinnick
wrote:
> On Wed, 2009-01-28 at 04:27 -0800, Vinay Sajip wrote:
> > I'd like to attach some user-defined meta-information to individual
> > model fields and have it also be available in the corresponding form
> > fields. Ideally, I'd have liked to have a ke
On Wed, 2009-01-28 at 04:27 -0800, Vinay Sajip wrote:
> I'd like to attach some user-defined meta-information to individual
> model fields and have it also be available in the corresponding form
> fields. Ideally, I'd have liked to have a keyword arg on the fields...
>
> class MyModel(models.Mode
I'd like to attach some user-defined meta-information to individual
model fields and have it also be available in the corresponding form
fields. Ideally, I'd have liked to have a keyword arg on the fields...
class MyModel(models.Model):
name = models.CharField(max_length=100, info=some_object
6 matches
Mail list logo
