Feiler - Introducing SQLite for Mobile Developers
Here you can read online Feiler - Introducing SQLite for Mobile Developers full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Berkeley;CA, year: 2015, publisher: Apress, genre: Home and family. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:Introducing SQLite for Mobile Developers
- Author:
- Publisher:Apress
- Genre:
- Year:2015
- City:Berkeley;CA
- Rating:3 / 5
- Favourites:Add to favourites
- Your mark:
Introducing SQLite for Mobile Developers: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Introducing SQLite for Mobile Developers" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
1. Getting Up to Speed with Databases and SQLite.-2. Understanding What SQLite Is ... -- 3. Working with the relationship model and SQLite -- 4. Using SQLite basics -- storing and retrieving data.-5. Using SQLite features -- What you can do with SELECT statements.-6. Using SQLite with PHP.-7. Using SQLite with Java (Android) -- 8. Using SQLite with Swift (iOS/Mac) -- 9. Using SQLite with Objective-C (iOS/Mac).-10. Exploring the simple database (used in chapters 10-12) -- 11. Using the simple database with a website (database example code included) -- 12. Adding the simple database to an Android app (using android.database.sqlite) -- 13. Adding the simple database to an iOS app (using Core Data) -- 14. Considering performance issues -- 15. Managing the SQLite life cyle.;This brief book is an introduction to SQLite for both iOS and Android developers. The book includes an optional introduction to SQL, a discussion of when to use SQLite, and chapters devoted to using SQLite with the most likely programming languages and then goes through adding a simple database to an Android or iOS app and finally a chapter on managing the apps life cycle. What You Will Learn: - The basics of SQLite - The SQL you need to use SQLite effectively - How to integrate a database into your mobile app. - How to maintain the app Who this book is for: This book is for Android or iOS developers who wish to use a lightweight but flexible database for their applications. It mobile development experience but does not assume anything but very basic database knowledge.
Feiler: author's other books
Who wrote Introducing SQLite for Mobile Developers? Find out the surname, the name of the author of the book and a list of all author's works by series.
K. L. JAMES
it-ebooks
![Jay A. Kreibich - Using SQLite : [Small. Fast. Reliable. Choose any three]](/uploads/posts/book/149624/thumbs/jay-a-kreibich-using-sqlite-small-fast.jpg)
Jay A. Kreibich
Adam Stroud
Kevin Languedoc
Patrick Alessi
Jason Wei
Introducing SQLite for Mobile Developers — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Introducing SQLite for Mobile Developers" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Jesse Feiler 2015
Jesse Feiler Introducing SQLite for Mobile Developers 10.1007/978-1-4842-1766-5_11. Getting Up to Speed with Databases and SQLite
Jesse Feiler 1
(1)
NY, US
Electronic supplementary material
The online version of this chapter (doi: 10.1007/978-1-4842-1766-5_1 ) contains supplementary material, which is available to authorized users.
Ask people to tell you words they associate with database and youll probably get big among the responses. Databases handle large amounts of data, and everyone knows that. How big? It depends whether you count the number of items in a database or the size of the items. The Library of Congress has 160 million items on 858 miles of shelving as of this writing. The catalog, which is based on a database, is available online at www.loc.gov/about/fascinating-facts/ . Theres no question among people who are interested in databases that the Library of Congress catalog is far from the largest database in the world. (In all likelihood, the largest databases are not visible to the public because they contain classified corporate and governmental information.)
This chapter provides an introduction or reminder about databases today and how they are used. If youve used databases in the past, much has changed, and if you havent used them much in the past, this chapter will give you a quick overview.
Moving Beyond Big
Beyond big , you should start thinking about databases as being structured and organized . In fact, as a mobile developer, the structured and organized aspects of databases are much more important than their size. From the earliest days of the Web in the early 1990s, web browsers have used databases to store and organize their data. What data, you may wonder? How do you think your browser is able to store your passwords for the web sites you visit? How do you think browsers store web pages in a cache so that they can be retrieved without a new network access when possible? And what about your preferences for default font sizes? Or the download folder for files you can change when you feel like it, and even, on many browsers, restrictions on certain users or types of users? These are just simple examples, but the principles apply even to the largest (and smallest) databases today.
Databases Are Structured and Organized
All those examples can be implemented with a database because all those items need to be structured and organized. Some of the items can turn into large amounts of data (particularly a browser history if you dont choose an option to clear out the old information occasionallyanother option that can be stored in a preference database), but some of the preferences listed are very small amounts of data: even with a fully modified file name for your download folder, 128 characters is enough to store that data element. Furthermore, most browsers store the name of your preferred download folder, but they dont store the history of download folders (last weeks preferred download folder, the folder you used last month, etc.).
In thinking about databases, big is often relevant, but very frequently its misleading. It is structure and organization that matter most.
And they matter a great deal to a mobile developer.
Precisely because mobile devices need to function in a world of constrained resources (e.g., limited storage space and battery power), structuring and organizing the data that is stored is particularly important. Built into a data management system are various optimizations that matter to databases large and small. For example, many databases can store character or string data. Such data is typically quite variable. Even if a database designer specifies that a text field can contain 50, 500, or 50,000 characters, behind the scenes trailing blanks are often discarded. The user (and even the developer) may never know this, but it makes the entire database function more efficiently. (Features like this function behind the scenes and they can be accessed and turned on or off by the database designer in many cases.)
Databases Are Smart
Being able to optimize storage to work with the presence or absence of characters in a text field is a powerful behind-the-scenes tool, but databases have intelligence built into them.
In most database engines today, the designer can specify many attributes of a field such as the following:
- Name . A name that is used internally is often quite different from the name that appears in the user interface.
- Type . You can specify that a certain database field must be an integer or a string or any other type that the database supports.
- Optionality . Some fields are optional, and you can specify that when you set up a database. (Many people have a car with a license number; many other people do not own cars.)
- Default values . A database can be set to provide a default valueeither a simple value or a calculated value based on other data in the database.
- Cardinality . Sometimes, there are multiple values for part of the database. (To continue the example, some people have no car, other people own a car, and others own several cars. Furthermore, some people own a car and a bike... you get the idea.)
- Value ranges . When the database designer specifies the database structure, a range of values for each field can be set. A drivers license identifier that consists of characters other than letters and numbers (depending on the locality) may not be allowed.
- Value relationships . You can move beyond value ranges in designing a database. You can create combinations of attributes and values so that, for example, a database can enforce a rule that an employee may be married (to one person or no one), but if the employee is married, the spouses employer cannot be the same as the employees employee. These restrictions in the database reflect policies, but there well may be exceptions (a supervisors approval), and the database can be designed to support a case like that.
These are just a few of the ways in which a database can be set up to enforce logical rules.
Perhaps at this point youre tempted to say, But I can do each of those things with a line or two of code. Thats absolutely true. But there are a couple of points to bear in mind.
Writing Code Is Just the Beginning
You can write the code to implement any of those conditions, but thats just the start. Over time, conditions change, users have suggestions, and the Power That Be (whoever that (or they) may be in your life) decides to change the rules for employment, cars, the conditions that apply to license plate numbers, or any other things that strike his or her fancy.
The code that took only a few lines of code and a couple of minutes to write needs to be rewritten. And, although there is no clear research on the matter, it seems that these changes take place at the last minute before a product (or version) launch and they must be done immediately.
Parlez-vous Python? Sprechen Sie Scala?
The line or two that implement the rules for one of the data conditions may have been written by someone whos no longer around. Even if you wrote them, time may have passed and you may not remember exactly what you were trying to implement (yes, commenting your code is a desirable feature, but life happens...)
Those few lines of code may have been modeled on some code from a friend that does exactly (or almost) what you want. Maintaining even the best-written code is a challenge for everyone involved from the first author to the updater to the manager andeventually the user or manager who asks for just a little tweak.
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Similar books «Introducing SQLite for Mobile Developers»
Look at similar books to Introducing SQLite for Mobile Developers. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
K. L. JAMES
it-ebooks
Jay A. Kreibich
Adam Stroud
Kevin Languedoc
Patrick Alessi
Jason Wei
Reviews about «Introducing SQLite for Mobile Developers»
Discussion, reviews of the book Introducing SQLite for Mobile Developers and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.