No, you get a different set of headaches. Drivers (e.g. JDBC drivers) are not intended for this sort of application.
You will have reliability problems, security problems, performance problems, problems upgrading your server once you have clients talking to it, because you can't upgrade all your clients at once, etc. You'll also have the problems getting the drivers to work on the Android platform, which lacks support for database drivers. I think it's probably possible to do, but since it's not a good thing to do, I don't know of anyone who has succeeded. I've seen a lot of messages from people who have tried and failed. Drivers are much too closely coupled to the database. A competent system administrator WILL NOT ALLOW YOU ACCESS to databases from outside their firewalls, for security reasons. You will normally would use database drivers when implementing the web server. Sqlite is an embedded server with its own API, but you could consider that a type of driver as well. But as I said earlier, a non-Sqlite database, such as MySQL, would be a far better choice for performance, scalability, and reliability reasons. Unfortunately, that means yet more stuff to learn. Fortunately, it's mostly fairly standard stuff, so you'll get to use what you learn later in your career -- but it's still something you'll need to learn up front. None of these things are that hard to learn, but it's a lot to learn all at once. Especially if you expected to do things one way, and are told you have to do them a different way. It'll be hard to switch your way of thinking. On Mar 19, 7:03 am, uday kiran <[email protected]> wrote: > Hey Bob,, > > Tell me one thing...instead of using Webservices,it is easy if we r > using Drivers.. > If we know which type of database they r using on server side,then we > can access that database using > related driver...so that the headache willl be reduced am i right??? > > what is the difference of using driver in place of Webservices???? > > On Mar 19, 1:16 am, Bob Kerns <[email protected]> wrote: > > > > > On Mar 18, 2:37 am, uday kiran <[email protected]> wrote: > > - So for communicatingdatabase(On remote server) from our > > application > > - it is compulsory to write a driver like odbc??? > > > No, ODBC (or JDBC) is at the wrong level. You do not want to be doing > > SQL over the network. > > > Instead, you want to create a web server that does the SQL -- and you > > just ask it questions (via HTTP GET) or give it commands (PUT, POST, > > DELETE). > > > If you already know Java well, a Java Servlet would be the easiest way > > to go -- running in a servlet engine line Tomcat. > > > Tools like Ruby on Rails are supposed to make this even easier, but > > will involve learning a new language. > > > You're going to have to go and do some studying, and look at a number > > of examples. I'm not going to look for a pointer to an example for > > you, because if you do it yourself, you can chose ones that more > > closely relate to what you're trying to do, or better fit your style > > of learning. > > > But you can start on the server side by writing a unit test that > > simply takes a URL, interprets the parameters, and does the > > corresponding SQL query, and returns the result as either XML or JSON. > > Once you have that, it's a simple matter to embed that in the > > appropriate bit of code for your web server technology (e.g. a > > Servlet, in the case of Java). The client side just requests the data > > from that URL and reads it. > > > Once you get that far for one kind of data, and the GET operation, the > > next steps will be both easier and more clear to you. Part of your > > problem right now is you're trying to deal with the entire question at > > once. -- 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 To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
