Re: "This is a limitation/shortcoming/"feature" of Android."
No, it's not. It's a characteristic of SQL database connections, vs the characteristics of distributed clients. This is not new with Android -- well-written desktop applications use a service layer rather than direct connection to the SQL database. There are many, many very important reasons for this, from performance and scalability to network reliability. But to my mind, the single most important reason for it is this: If you change your database schema for whatever reason, you are not able to force all of the clients to synchronously update to use that brand-new schema. Yes, you can use views, triggers, and such to try to mask such changes, but they're both extremely awkward to maintain and quite limited, and often negate the very benefit you wanted to achieve with the schema change. I would even agree with Miguel's formulation, that "Any decent developer should know this" -- if you take it as advice. This is core architectural savvy that if a developer is not familiar with, he should seek to remedy. And -- despite it not being useful in this way -- I would also say that a solid knowledge of SQL is something any well-rounded developer should acquire. Put them on the list with all the others... But the bottom line is, the advice to not use SQL this way has nothing at all to do with Android, or Java. And only a bit to do with being on a mobile device. On Aug 21, 11:53 am, DanH <[email protected]> wrote: > "Any decent developer should know this." > > That's unfair. The OP did state that he was new to Android, and on > other platforms you CAN connect directly to a remote database. This > is a limitation/shortcoming/"feature" of Android. > > On Aug 21, 1:24 pm, Miguel Morales <[email protected]> wrote: > > > > > Don't connect to mysql directly from the android device. > > Any decent developer should know this. You'll have to create a web > > frontend for your data/app probably using a RESTful style. > > >http://code.google.com/events/io/2010/sessions/developing-RESTful-and... > > > On Sat, Aug 21, 2010 at 11:05 AM, Frank Weiss <[email protected]> wrote: > > > Out of the many ways to interpret your question, I'm going to assume > > > your Android app needs to query certain data you have in a MySQL > > > database running on a server on the internet. > > > > The typical way that's done is add a web service on that server that > > > performs the SQL queries locally and returns XML or JSON data to the > > > Android app. > > > > I suppose it would help if you explained how data in that database is > > > currently being accessed. > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Android Developers" group. > > > To post to this group, send email to [email protected] > > > To unsubscribe from this group, send email to > > > [email protected] > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en > > > --http://developingthedream.blogspot.com/,http://diastrofunk.com,http:/..., > > ~Isaiah 55:8-9 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
