Comments for Inphina Thoughts

Comment on Take care of Version Number while Deploying on Google App Engine by Narinder Kumar

Narinder Kumar — Sun, 22 Jan 2012 12:13:42 +0000

Dear Ram,

Happy to know that the post helped you in some ways. FYI : I am based out of New Delhi, India.

Comment on Take care of Version Number while Deploying on Google App Engine by Ram

Ram — Sat, 21 Jan 2012 17:54:22 +0000

Dear Bro, Where are you?

You solved my issue. Thank you so much. ..Ram

Comment on Using RDBMS on Google App Engine : Google Cloud SQL by Narinder Kumar

Narinder Kumar — Sat, 07 Jan 2012 08:02:30 +0000

Thanks for the update JT.

The application being in preview and Invite-Only mode, we should not expect it to be Production Ready. The idea is to have users test, provide comments and feedback to make it more complete.

Comment on Using RDBMS on Google App Engine : Google Cloud SQL by Narinder Kumar

Narinder Kumar — Sat, 07 Jan 2012 07:59:38 +0000

I have not done any of these tests but based upon my earlier experiences, Google Datastore is designed for massive scalability. The point here is whether your application is suitable or requires those features. When we need lot of relational constraints and consistency is more important than speed, RDBMS makes more sense over NoSQL. What CloudSQL provides is a solution for these situations where we don’t have to worry about replication, data-sharding, fault-tolerance etc.

Comment on Getting Started – Scala Persistence with Squeryl by Bert

Bert — Fri, 06 Jan 2012 23:35:54 +0000

I’d say that your model is *not* a POSO as “Plain Old” means “does not extend or implement framework types. But your model extends org.squeryl.KeyedEntity.

Comment on Using RDBMS on Google App Engine : Google Cloud SQL by JT (@jtantwtr)

JT (@jtantwtr) — Fri, 06 Jan 2012 23:20:46 +0000

We tried CloudSQL using Hibernate 4 and we encountered the following error frequently -

23:16:38,720 WARN SqlExceptionHelper:143 – SQL Error: 0, SQLState: null
23:16:38,721 ERROR SqlExceptionHelper:144 – Could not fetch URL: https://www.googleapis.com/sql/v1/jdbc/exec?alt=proto

With ends results and commit failure during save/update. I think this product is definitely not ready for production usage. The concept is cool though.

Comment on Using RDBMS on Google App Engine : Google Cloud SQL by aglassman

aglassman — Fri, 06 Jan 2012 17:37:50 +0000

How is the speed of Cloud SQL vs the datastore for large datastes? I’d assume it would be slower and harder to scale. A RDBMS would be nice for smaller apps so I might have to look into testing out the Cloud SQL service.

Comment on Why Unowned Relationships Make More Sense With App Engine Datastore by aglassman

aglassman — Fri, 06 Jan 2012 17:31:33 +0000

After attempting to mess with the JDO api, I think i’m going to switch to Objectify, and just use mostly unowned relationships. The JDO api seems to be more trouble than it is worth for complex relationships. Better to rethink the data layer like you have above. Thanks for the insight!

Comment on Using RDBMS on Google App Engine : Google Cloud SQL by Using Google Cloud SQL

Using Google Cloud SQL — Fri, 16 Dec 2011 14:14:38 +0000

[...] == "undefined"){ addthis_share = [];}This blog post provides information on how to use the Google Cloud SQL database on Google App Engine. Google Cloud SQL is web service that allows you to create, configure and use relational databases [...]

Comment on Working With Spring Data JPA by jaggs

jaggs — Fri, 02 Dec 2011 11:29:16 +0000

EmployeeRepositoryImpl : implementing EmployeeRepository interface that means we need to override all methods in Parent interface(JpaRepository) otherwise won’t compile the code.
But if we override all methods of JpaRepository then what is the use of JpaRepository.