Thank you guys!
2008 seems fine.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send
Hi GAE Team,
we have a stable self programmed CMS running on the GAE (Java). The
software runs fine, and we haven't done any program changes in the last
couple of days.
Yesterday (2014-09-29) colleagues of mine entered lots of data, which
where successfully stored in the database.
Today, all
If you don't mind sharing, what was the quota limit that you reached? I
want to use Prospective Search, but I can't figure out whether I am going
to hit the limit or not. The documentation isn't very clear on this.
On Tuesday, September 16, 2014 5:13:10 PM UTC+2, Appsent Minded wrote:
>
> My app
Hi,
I use the free quotas app engine and it keeps returning the following error
9 times out of 10:
Object {0: "Developer Over Qps"}
As I understanding, there is no limitation on the Qps, even with the free
plan.
Any way, even querying my app every 1-2s is too much apparently.
Any idea what c
I'm trying to set up my new website using *Google App Engine (PHP)*. I have
bought the domain and my website is working fine. Well, kind of. I have two
forms on my website, one asks for just an email and other a contact form.
Both of them accepts input but can't send the input to where they
I need an scalable database, and i know that NoSQL is the best option for
that, but i also need an interface that will help me observe my data with
some complex sql query, and SQL is the way to do so, but i don't know how
to use SQL & NoSQL together.
According to Google I/O 2012 - SQL vs NoSQ
Has your problem resolved yet ?
I am having similar issue connecting to GCS from AppEngine from a new app
(its working for my old/legacy app)
The problem seems to be of credentials for service account for App Engine
are missing in any new cloud project.
There is a stack overflow thread on
this
Hi,
I have created a new App Engine app last week and through that I am not
able to access GCS (Google Cloud Storage) bucket which is part of the same
cloud project.
I am getting following errors
W 08:21:29.581
suspended generator _make_token_async(rest_api.py:101) raised
InternalError(1: )
I am using sign-up/sign-in with Google feature in my app, but when I deploy
the my app in google app engine then I am getting following error.
org.apache.http.impl.client.DefaultRequestDirector tryConnect: I/O
exception (java.net.SocketException) caught when connecting to the target
host: Per
Hi
what is the best practice if i want to update n-register in relationship
with ndb.StructuredProperty?
thank you.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an
I created an issue
https://code.google.com/p/googleappengine/issues/detail?id=11332
but I was hoping someone here could help me
I can't seem to get a storage bucket to work with php.
I'm running the following code:
https://github.com/jamesjnadeau/gae-storage-test-hardcoded-2
here:
http://a
The question was answered
here: http://stackoverflow.com/questions/26120766/developer-over-qps/26134157
( "Object {0: "Developer Over Qps"}" was returned by 3rd party API, not by
GAE).
On Tuesday, September 30, 2014 7:25:17 AM UTC-5, Nicolas Rannou wrote:
>
> Hi,
>
> I use the free quotas app
On Wed, Oct 1, 2014 at 3:39 AM, Shankar wrote:
> I am using sign-up/sign-in with Google feature in my app, but when I
> deploy the my app in google app engine then I am getting following error.
>
> org.apache.http.impl.client.DefaultRequestDirector tryConnect: I/O
> exception (java.net.SocketExc
On Tue, Sep 30, 2014 at 7:25 AM, Nicolas Rannou
wrote:
> I use the free quotas app engine and it keeps returning the following
> error 9 times out of 10:
> Object {0: "Developer Over Qps"}
>
As Mihail said, it looks like you crossposted this question to Stack
Overflow and received the correct
On Thu, Oct 2, 2014 at 3:52 AM, wrote:
> Thank you guys! 2008 seems fine.
>
If I recall correctly, datastore was a founding feature of App Engine,
baked in since the beginning. So you could also say since launch.
App Engine's early marketing materials didn't directly refer to the
datastore - i
On Tue, Sep 30, 2014 at 2:03 PM, Jonathan Solorzano <
jonathanfelixsolorzanofuen...@gmail.com> wrote:
> I need an scalable database, and i know that NoSQL is the best option
> for that, but i also need an interface that will help me observe my data
> with some complex sql query, and SQL is the w
On Thu, Oct 2, 2014 at 6:34 AM, Anmol Parashar <4nm0...@gmail.com> wrote:
>
> I have two forms on my website, one asks for just an email and other a
> contact form. Both of them accepts input but can't send the input to where
> they are supposed to. A message is displayed, "PHP scripts/files are
Per release notes the 1.0.1 release happened on Apr. 14, 2008. If you scroll up
a bit you see that the release notes of 1.1.0 (on May 29, 2008) state among
other things:
“...Fixed Datastore API to allow …”
OK I think we have put this to rest :-)
(Of course the datastore was later significantly
18 matches
Mail list logo