Did the "custom_qualifier" patch make it into root?
I can see it is used in dal/pydal/adapters/google_adapters.py but with any
values passed straight through it's not easy to work out what is/isn't
supported.
On Sunday, 10 March 2013 02:51:11 UTC, Christian Foster Howes wrote:
>
> Massimo, Scot
Massimo, Scott,
i filed https://code.google.com/p/web2py/issues/detail?id=1373 with a patch
against trunk. Looks like my first patch on this thread made it to the
latest release, but the second patch did not. If that can be applied i
think we'll be all set.
perhaps i now need to start submit
Sorry, I thought I had -- it works like a champ. Would be nice if there
were a way to mark the signature fields as unindexed w/o having to recreate
them (not as simple as cut and paste, as the table def uses a bunch of
local definitions, but not hard), but definitely workable. And lowers the
can you let me know if it works as desired now? if so, i'll submit the
patch to massimo for review and possible inclusion in the next release of
web2py.
thanks,
cfh
On Tuesday, February 26, 2013 6:31:52 PM UTC-8, Scott Hunter wrote:
>
> With the latest patch, I was able to disable indices on
With the latest patch, I was able to disable indices on the string fields I
wanted to. Unfortunately (for me), I've just about used up my quota, so
I'll have to wait until tomorrow to see how much doing so saves me.
Thanks,
Scott
On Tuesday, February 26, 2013 8:50:29 PM UTC-5, howesc wrote:
>
oh, and about the "web2py-supplied fields", those come from auth.signature,
which is just a table that you "inherit" from. from gluon/tools.py you
see the auth.signature definition as:
self.signature = db.Table(
self.db, 'auth_signature',
Field('is_active', 'boo
here's an updated DAL patch to try.
thanks for trudging through this with us!
cfh
On Tuesday, February 26, 2013 3:36:30 PM UTC-8, Scott Hunter wrote:
>
> I'm working from Version 2.3.2 (2012-12-17 15:03:30) stable
>
> Here's the table in question (I've commented-out the custom_qualifier for
I'm working from Version 2.3.2 (2012-12-17 15:03:30) stable
Here's the table in question (I've commented-out the custom_qualifier for
the string fields):
db.define_table('t_run',
Field('f_trial', type='reference t_trial',
label=T('Trial')),
Field('f_when', type='date',
your line numbers are off from mine so i'm having trouble making sense of
this. :(
can you send your model definition so i can see what you are working with?
i think then i can line it up with the dal version i have here (which was
trunk from HG as of saturday AM PST)
cfh
On Tuesday, Februar
Sorry about that. I've fixed it, and now I get the following:
In FILE: /base/data/home/apps/s~sbhweb2py/1.365574604253984974/applications/
ppt_demo/models/db_wizard.py
Traceback (most recent call last):
File
"/base/data/home/apps/s~sbhweb2py/1.365574604253984974/gluon/restricted.py",line
2
it looks like you have a typo "custom_qualifer" vs "custom_qualifier"
On Monday, February 25, 2013 6:44:14 PM UTC-8, Scott Hunter wrote:
>
> I applied the patch, and added custom_qualifiers like so:
>
> Field('f_name', type='string',custom_qualifer={'indexed':False},
> label=T('N
I applied the patch, and added custom_qualifiers like so:
Field('f_name', type='string',custom_qualifer={'indexed':False},
label=T('Name')),
and this is the error I got:
In FILE: /base/data/home/apps/s~sbhweb2py/1.365567821359373728/applications/
ppt_demo/models/db_wizard.py
Tr
Scott,
this is *completely* untested, but here's a proposal:
- use the (undocumented) field.custom_qualifier property in GAE field
definitions
- if you want a field to be unindexed set
custom_qualifier={'indexed':False}
- for "properties that don't get listed explicitly"override those
de
If I had to guess, I'd say a patch is needed in the loop over the fields in
create_table, that would add a new entry to the dict for the field
definition based on a new attribute (which would be ignored for anything
other than Google's Datastore) which gets added to sql_fields; then
migrate_tab
thanks for the link. i'll try and take a look this weekend and see if
there is a place for that in the DAL (feel free to open gluon/dal.py
yourself too).
yup, i'm paying more for writes right now then i am for instance hours per
day on my largest paid application. :)
cfh
On Thursday, Februa
According
to
https://developers.google.com/appengine/docs/python/datastore/indexes#Unindexed_Properties,
"You declare a property unindexed by setting indexed=False in the property
constructor".
One incurs the cost of a write (or 2?) for every property of a record that
gets written; so, for a
i'm being lazy heredo you have the instructions (or link to
instructions) from GAE for disabling indexes? i don't have it handy right
now
we can check if the DAL has a secret way to handle it, and/or create a
patch to allow it.
may i ask what advantage you are hoping to achieve by ski
17 matches
Mail list logo
