note that unless the book calls out google:sql vs google:datastore it's
referring to google:datastore. SQL was added much later by google, but
it's a mysql compatible database, and so should have most (perhaps all?)
the mysql features.
On Tuesday, March 12, 2013 2:14:39 AM UTC-7, decu...@uemd.
> What do you think? Could this work? Will web2py auth support this?
>
If the google:sql adapter supports joins (which I belive is the reason for
the accessible_query restriction), and I think it does, there should be no
problem, but I never tried it.
The issue is how to deal with access contr
Hi all,
i've been slow on this partially because i'm in the middle of some giant
re-factorings to optimize for the new pricing model on GAE. here are some
thoughts:
- memcache is your friend. if you are querying for something on a
request, toss it in memcache (you have to cast rows to dicts
Christian,
Did you manage to write this? I am looking for optimizing the GAE. Would
appreciate your inputs.
Thanks,
Joseph
Thanks, that would be much appreciated!
On Oct 27, 3:28 am, howesc wrote:
> i will write something up for you soon
i will write something up for you soon
On Oct 25, 2011, at 12:29 PM, Damjan Malis wrote:
> Jonathan,
>
> logging.conf file
>
> [loggers]
> #keys=root,rocket,markdown,web2py,rewrite,app,welcome
> keys=root
Thanks. That's interesting.
>
>
>
> On Oct 25, 9:13 pm, Jonathan Lundell wrote:
>> On Oct 25, 2011, at 10:31 AM, Damjan Mali
Jonathan,
logging.conf file
[loggers]
#keys=root,rocket,markdown,web2py,rewrite,app,welcome
keys=root
On Oct 25, 9:13 pm, Jonathan Lundell wrote:
> On Oct 25, 2011, at 10:31 AM, Damjan Malis wrote:
>
> > Hi Christian, thanks for your informative reply.
>
> > You were right, I do use URL and
On Oct 25, 2011, at 10:31 AM, Damjan Malis wrote:
> Hi Christian, thanks for your informative reply.
>
> You were right, I do use URL and A quite a lot, and most of LOGs come
> from that two helpers. I also managed to completely turn off logging
> by modifying logging.conf.
That's good to kno
Hi Christian, thanks for your informative reply.
You were right, I do use URL and A quite a lot, and most of LOGs come
from that two helpers. I also managed to completely turn off logging
by modifying logging.conf.
Interesting, today my website is performing much much better - without
any changes
Damjan,
i use GAE heavily, here's what i can say based on what i see:
- each call to URL() puts at least one message in the debug log. so
whatever you are doing has lots of calls to URL() in it.
- logging can be affected by logging.conf, but i've never successfully
suppressed logs i didn't ca
Yes, I am certain that all slow requests include log msg "no file
locking, this will cause problems". Also, it is very rare, but some of
requests fail after "no file locking, this will cause problems" as GAE
kills such request because of time limit is reached (60sec). I will
most definitely gather
On Oct 24, 2011, at 11:20 AM, Damjan Malis wrote:
> Thanks Jonathan for clarification.
>
> I am attaching full GAE log of one of the requests, please find it
> below. It is quite verbose, did I miss an important setting to lower
> log level?
GAE has its own logging rules. I think it ignores the
It should.
On Oct 24, 10:28 am, Jonathan Lundell wrote:
> On Oct 24, 2011, at 8:01 AM, Damjan Malis wrote:
>
> > Hi guys, I'm having difficulties running simple app on GAE. I've
> > created simple controller that selects all records (15) from table and
> > passes them to my view. View just lists
Thanks alot :)
On Oct 16, 12:54 am, Massimo Di Pierro
wrote:
> You should not use local_import. It is deprecated and anyway not
> designed for this.
>
> Just put the packages in site-packages, and use normal import. site-
> packages is in sys.path.
>
> On Oct 15, 8:54 pm, Minocha wrote:
>
>
>
>
try moving app.yaml to web2py/app.yaml that's where i keep mine.
Are you able to post more details of the errors you get?
Generally it works as expected (but with some caveats on the GAE
side).
We've currently going through that exercise, and noting that there
could issues with SQL cloud which we haven't resolved yet
(i.e. runs nosql OK but not mysql)
On Oct 1
You should not use local_import. It is deprecated and anyway not
designed for this.
Just put the packages in site-packages, and use normal import. site-
packages is in sys.path.
On Oct 15, 8:54 pm, Minocha wrote:
> I used the local_import function after copy-pasting the module
> directory into t
I used the local_import function after copy-pasting the module
directory into the [application-name]/packages/ folder but even then i
get an error.
Please help
On Oct 15, 4:57 pm, Minocha wrote:
> i'm new in deploying applications on the GAE using the web2py.
> I wanted to ask what is the procedu
for libraries that GAE does not provide, put them in a site-packages folder
just inside the web2py folder. They will then be on your path. it is up to
the user to ensure that the libraries that you include follow the GAE rules.
Yes, the django-nonrel leader made a clear separation between micro-
frameworks and the bigger ones (apps speed versus development speed
and reusability)
-
On 8 Set, 14:45, Richard wrote:
> seems you are referring to this
> thread:http://groups.google.com/group/google-appengine-python/brows
seems you are referring to this thread:
http://groups.google.com/group/google-appengine-python/browse_thread/thread/fad46eb3745c39c2
On Sep 8, 10:25 pm, Peterle wrote:
> considerations of..
>
>
> On 8 Set, 13:57, Peterle wrote:
>
> > google-appengine-python group, Google Appengine Python B
considerations of..
On 8 Set, 13:57, Peterle wrote:
> google-appengine-python group, Google Appengine Python Best Framework:
> what's about web2py? Interesting the valutations of Waldemar.
23 matches
Mail list logo
