Hi Andy,
It's possible you could do this (though not using the code below), but it
seems like it would be easier to just use a db.Expando model? I can't see
any advantages to consistently having the same property name use two
different types.
-Marzia
On Mon, Nov 17, 2008 at 12:56 PM, Andy Freeman <[EMAIL PROTECTED]> wrote:
>
> Since neither db.Text nor db.Blob is indexed, can we decide between
> them on an entity-specific basis?
>
> Specifically:
>
> class A(db.Model):
> a = CustomProperty()
>
> # where CustomProperty takes its data_type for get_value_for_datastore
> purposes from the value, not from CustomProperty's definition.
>
> a1 = A()
> a1.a = db.Text('hi')
> a1.put()
> a2 = A()
> a2.a = db.Blob('there')
> a2.put()
>
> Will the datastore have some problem with the fact that a1's a
> property db.Text while a2's a property is db.Blob?
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
