Author: Michał Kołodziejski

Senior Software Engineer

Using an SQLite Database on Android Platform A Short FAQ

When developing an application with a SQLite database as persistent storage, it’s worth it (or necessary, in fact) to know some low-level details like: where the data is storedphysicallyand 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.

Handling Database Structure Changes

In the previous article we wrote a simple Android app allowing the user to manage his ToDo list. He could add new tasks, mark them as done and delete them. That article 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, we distribute it (i.e., it shows up in Google Play), people download and use it. After some time we decide to improve the app. Our goal is to add the ability to prioritize the tasks.

Using an SQLite Database on Android Platform – Introduction

According to the report of the International Data Corporation , Android operating system reached more than 80% market share during the 3rd quarter of 2013. Together with iOS, Android 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

Designing a Database: Should a Primary Key Be Natural or Surrogate?

Suppose we design a database. We’ve created some tables, each one has a few columns. Now we need to choose columns to be primary keys (PK) and make references between tables. And here some inexperienced designers face the dilemma – should a primary key be natural or surrogate?There’s one and only one answer to that question:it depends. If anyone ever tried to convince you that you should have only natural keys or only surrogate keys, just smile :)

Good news: we now support views

Today we are happy to announce that Vertabelo has a new feature we’ve been working on for some time –views. Now you can easily add them to the diagram, change their definition and other properties and have them generated in your SQL scripts.Quick overview of viewsLet’s take a look at how simple it is to create a new view in our editor.Our goal is to make a view which joins three tables as follows:

Vertabelo in Dublin: PGConf EU 2013

As those following our Twitter feed know, last week we were in Dublin, Ireland at the PostgreSQL Conference Europe 2013 as a Silver Sponsor. Since this conference and the host country were new to me, I thought I’d share some quick reflections on the experience.The conferenceAll of us on the Vertabelo Team are intimately involved with databases. Not only do we routinely design and use databases, we even built a tool to create database models. We know all of the good and bad practices (AKA patterns and antipatterns) used in database model design. We speak fluent SQL (some may say even better than we speak English!). Given our profound relationship with databases, we had quite high expectations for the PGConf EU.