Got it. I will look into creating such option. The issue is to make it general enough
On Jun 24, 12:06 pm, NickFranceschina <[email protected]> wrote: > yes that's what I'm saying... there must be some code in Web2py where > if the field is 'upload' and you're running on GAE, then it triggers > creation of the blob field... but probably shouldn't create the blob > in the same table, since on GAE there is no way to NOT load the blob > (it always loads the entire object) > > maybe this isn't a big deal to GAE... it can handle alot... but it > requires my touching every object that has an upload field before > passing it back through JSON (have to set blob fields to null first) > > On Jun 23, 2:50 am, mdipierro <[email protected]> wrote: > > > > but as for automating the schema maintenance... if I create > > > auth_user.Field('photo','upload') > > > instead of creating a 'photo' (string) and 'photo_blob' (blob) on the > > > same table, it should maybe create just 'photo' (string) and another > > > table called 'auth_user_photo' with one field and a reference? > > > Field('photo','upload') is always a string. On GAE it also triggers > > the creation of a the blob field in the same table.
