there are many differences between traditional relational databases (like mysql) versus non-relational databases, aka nosql (like gae's datastore)
but yes, "Full-text search over Datastore" is coming really soon App Engine Product Roadmap http://code.google.com/intl/en/appengine/docs/roadmap.html Google I/O 2011: Full Text Search Bo Majewski, Ged Ellis http://www.youtube.com/watch?v=7B7FyU9wW8Y (I recommend everyone here to take a look at it, it's really nice) there were 2 main problems when I switched from my traditional mysql- thinking to datastore-thinking: geo search and full text search. the first is solved using GeoModel (made by some fine Google employees), the second will come as a Google solution (see the video). so I'm extremelly happy with GAE :) I hope you enjoy it too, Bruce. On Sep 28, 10:18 am, Niklas Rosencrantz <nikla...@gmail.com> wrote: > These are among the drawbacks, minuses and reasons why app engine should be > cheaper than traditional hosting: > - no join, no like, no full text search while sql-based system have these > - extremely difficult to migrate from M/S to HRD while sql-based system > usually can migrate even large blobs > - sitemap.xml.gz has no good solution, you have to roll your own whereas > legacy systems have ready solution to make a sitemap > - admin console with federated login breaks (other have phpmyadmin or tons > of other solution while I don't have a backup system so my system is not > real) > - "it's not good but it's the best we got"? regards \niklas -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
