On 31 Mar 2010, at 02:38, David Sowerby wrote:
Now all
I have to do is decide which of the alternatives to go for .
Twig has the prettiest representative... however she has a very
negative attitude towards traditional persistence interfaces on the
datastore:
http://code.google.com/
i switch from JDO to Objectify i one Day.
i changed 42 classes (thats what my svn says), but the key to success the
migration was the tests:
57 green tests before start + 1 factibility test for objectify in
transaction.
Now my code is clean y work faster,
NM
On Tue, Mar 30, 2010 at 4:38 PM, Da
Andreas, first thanks for the article, it was hugely interesting and
of course thanks to all who have given us some alternatives to argue
about! A few themes seem to come out of this for me
1) Some people are just either happier with what they know (SQL/
RDBMS) - perfectly understandable and pro
On Tue, Mar 30, 2010 at 8:03 AM, Guillermo Schwarz
wrote:
>
> SQL can be run on top of a file system (fseek, read, write) or on top of a
> persistent hashmap (datastore).
>
> If you create a SQL interface on top of any of those, then it is a
> relational database, not a fake but a real relational
First of all, please accept big thanks, Andreas. Those knowledge sharing is
helpful to me as well as other learners.
Follow the thread, I think I was a bit misled on benefit of SQL/JDBC on GAE.
In Andreas blog's, he mentioned on learning curve to deal with the mapping:
Java classess <--> JDO/JPA
Oops. A bit tired here. I wrote SQL in some places where I actually
meant jiql/cloud2db.
On Mar 30, 5:58 pm, Andreas Borglin wrote:
> These misunderstandings :-).
>
> I wouldn't say that computer science is about building
> abstractions..perhaps software engineering. (Dijkstra would have said
> l
These misunderstandings :-).
I wouldn't say that computer science is about building
abstractions..perhaps software engineering. (Dijkstra would have said
less kind words than me about that :-) )
Anyways, as much as I agree that abstractions are nice, have you
actually used AppEngine with these f
Hi Guillermo,
> If you create a SQL interface on top of any of those, then it is a
> relational database, not a fake but a real relational database. Why would I
> want a relational database? Consistency, for starters. ACID transactions.
> Set operations.
'Consistency' is a broad term. If you are
Hi Guillermo,
I agree with you completely. Here are my thoughts on the subject.
Relational theory, SQL and JDBC are functional specifications and RDBMS
vendors implement these specifications. Actually speaking data model has
nothing to do with technology. A data model in software engineering is a
Andreas,
I think there is more misunderstanding again.
SQL can be run on top of a file system (fseek, read, write) or on top of a
persistent hashmap (datastore).
If you create a SQL interface on top of any of those, then it is a
relational database, not a fake but a real relational database. Why
Thanks Nick :-).
On Mar 30, 12:53 pm, "Nick Johnson (Google)"
wrote:
> Hi Andreas,
>
> Excellent article! I've posted it to the App Engine
> reddit:http://www.reddit.com/r/AppEngine/comments/bk4kt/datastore_frameworks...
>
> Please feel free to post the followup article(s) there, too, to make su
Sandeep,
Please read Andreas article (link is in the first post of this thread):
"The interview article has now been published and can be found at
http://borglin.net/gwt-project/?page_id=604 ."
It would be nice if the article included CloudDB too.
Cheers,
Guillermo.
On Tue, Mar 30, 2010 at 9:1
Ok, you seem to misunderstand me quite a bit here.
I never said it can't be used. I just said that I don't want to.
Other than for portability reasons, why would I want to pretend that
the datastore is relational by using a framework that emulates this?
My main requirement, which was formed afte
Andreas,
I don't get it. You can use JDO and Hibernate with SQL. Given that
jiql has a Hibernate config file, I guess using Hibernate with jiql
would be so easy.
What does GWT and JSP have to do with SQL anyway?
Cheers,
Guillermo.
On 30 mar, 03:51, Andreas Borglin wrote:
> Hi again.
>
> I had
Hi,
You can try Cloud2db also. Please see the website http://www.cloud2db.com.
This works with any JDBC client tools/frameworks like Squirrel,
PowerArchitect, Hibernate in a client/server mode. This also works on Google
App Engine server with native JDBC driver.
Thanks,
Sandeep.
On Tue, Mar 30,
Hi again.
I had a look at jiql.
"jiql is a JDBC wrapper for accessing Google DataStore on Google App
Engine for JAVA.
jiql supports the use of standard SQL as a method for accessing
the DataStore"
Even if I had seen jiql earlier I wouldn't have considered it anyway
because,
1. I want the API to
Hi Guillermo.
Well, it's hard to consider things that I didn't know existed :-).
I was only aware of the six frameworks that I mentioned in the post.
I'll take a look at it.
On 29 mar, 20:52, Guillermo Schwarz
wrote:
> One question: Why didn't you consider jiql?
>
>
>
> On Mon, Mar 29, 2010 at
One question: Why didn't you consider jiql?
On Mon, Mar 29, 2010 at 1:04 PM, Blake wrote:
> +1
>
> On Mar 29, 4:03 am, Andreas Borglin wrote:
> > Hi all.
> >
> > I recently decided to migrate away from JDO to one of the third party
> > datastore frameworks. At first I had only heard about objec
+1
On Mar 29, 4:03 am, Andreas Borglin wrote:
> Hi all.
>
> I recently decided to migrate away from JDO to one of the third party
> datastore frameworks. At first I had only heard about objectify, but
> after some further digging I found out about 5 other frameworks as
> well (Twig, SimpleDS, si
19 matches
Mail list logo
