Storage engines can surprise you. For example, take the CHAR data type. It expects an exact number of characters and by definition stores a fixed amount of information. However, you don’t have to fill all the available CHAR space – a shorter value will work. This is so similar to VARCHAR that I decided to explore the differences between these two types.
The most common way to implement database functionalities in iOS applications is definitely Apple’s Core Data. However, its architecture is really Apple-like: it doesn’t let you see anything happening inside and the structure is hidden from you. That’s why some people dislike Core Data and prefer to stick with an SQLite database – even though SQLite is not supported natively.
Although mobile apps do not rely on databases as much as, say, web applications, mobile app developers should still be interested in databases. There are better database solutions for Android apps than a native SQLite library; we’ll nominate ORMs as one of them. In this article, we’re going to take a look at some of the most popular Android ORMs: ORMLite, ActiveAndroid, greenDAO, and Sugar ORM. We’ll also check out our new Vertabelo Mobile ORM.
Anyone who had to schedule an intercontinental phone call knows that there is no such thing as a simple time called now. What you should rather think about is a time comprised of here and now. The Earth rotates around its own axis. When it's solar noon (the sun is at its highest position) in one place, it's already past noon in places to the east and it's still before noon in places to the west.
SQL has been around for decades and supports a many billion dollar market. However, many people still struggle with just how to pronounce the term SQL.
Is it ”S.Q.L” [ˈɛs kjuː ˈɛl] or is it ”sequel” [ˈsiːkwəl]?
Let’s start at the beginning, i.e., when relational databases came into existence ...
The Vertabelo journey continues … We now have almost 10,000 users and the number of Vertabelo advocates keeps growing strong.
Vertabelo users come from over 100 countries and speak various languages. What unites them? The relational database.
Let’s see what relational databases they use ...
When developing an application with a SQLite database as a persistent storage, it’s worth it (or necessary, in fact) to know some low-level details like: where the data is stored physically and how we can determine if its structure is really the same as what we expect it to be. Being familiar with these things makes it easier and faster to develop, as well as find and fix bugs. I'll try to explain some of the most frequently asked questions regarding SQLite databases.
In the previous article we wrote a simple Android app allowing the user to manage his ToDo list. We showed how to create an SQLite DB in an automated way and how to do some simple CRUD operations on it. Let’s say that the first version of an application is released and people use it. Now, after some time, we decided to improve the app. Our goal is to add the ability to prioritize the tasks. What do we need to do?
Generally, we don’t limit query results. However, when we only care about the first few rows or to implement table pagination, limiting query results is just what we need. Database vendors provide us with such functionality; most of them in their own distinct way.
Indisputable fact is that Android, together with iOS, dominates in the mobile devices’ world. This made me think that it may be worth writing a few words about how to create mobile applications for these two mobile platforms. But not the kind of “hello world” applications – there are plenty of tutorials about that. I’d like to focus on the use of local SQLite databases.