tags: database, PostgreSQL

Action executed in 0.000

Each Tag

database, PostgreSQL

Common tags - number of posts

TrickleUp (3), ERD (3), OSM (3), blog (2), map (2), nutrition (2), planet (2), tuning (2), regex (2), import (2), GIS (2), beer (2), Python (2), Akonadi (2), TIGER (2), programming (2), PostGIS (2), index (2), model (1), pgsnapshot (1), RAID (1), CHART (1), JpGraph (1), library (1), pnorman (1), procedural language (1), exception handler (1), food (1), user input (1), software (1), disk (1), fiction (1), recipes (1), render (1), normal form (1), changeset (1), comment (1), aggregation (1), PHP (1), number (1), Xerces (1), DC (1), scrape (1), graph (1), PowerMac G5 (1), upgrade (1), traffic (1), fan (1), up-to-date (1), manager (1), kernel (1), query (1), speed (1), scan (1), citext (1), text (1), mapnik (1), case (1), osm2pgsql (1), interactive (1), comments (1), address (1), tile (1), Areca (1), osmosis (1), Linux (1), XAPI (1), jxapi (1), devops (1), Elwing (1), bug (1), femenism (1), USDA (1),

Sub groups 1

PostgreSQL (2), PostgreSQL, index, regex (2), database, fiction, interactive (1), database, food, manager, nutrition, recipes, scan (1), PHP, PostgreSQL, procedural language (1), USDA, database, nutrition (1), GIS, PostgreSQL, library (1), OSM, Python, changeset, database (1), TrickleUp, blog, database (1), OSM, PostgreSQL, XAPI, import, jxapi, osmosis, pgsnapshot, planet, pnorman, tuning (1), TrickleUp, blog, comment, database (1), Elwing, PowerMac G5, database, fan, normal form, upgrade (1), Areca, Linux, PostgreSQL, RAID, disk (1), PostgreSQL, aggregation, query (1), database, exception handler, number, software, user input (1), DC, GIS, address, database (1), CHART, JpGraph, Xerces, database, graph, scrape, speed, traffic (1), PostgreSQL, Python, devops, femenism (1), OSM, PostgreSQL, import, mapnik, osm2pgsql, planet, render, tile, tuning, up-to-date (1), TrickleUp, bug, comments, database, kernel (1), ERD, database, model (1), PostgreSQL, case, citext, text (1)


Akonadi: Database Design

Akonadi ERD

This is an overview of the database layout of the storage server. The schema gets generated by the server using the helper class DbInitializer, based on the definition found in server/src/storage/akonadidb.xml.

url: http://api.kde.org/kdesupport-api/kdesupport-apidocs/akonadi/html/akonadi_server_database.html

type: article, format: blog


After a long day at work of arduous programming, i come home to do what? Yes more programming. But wait there's a difference. At home, i can sip my beer while waiting for code to compile.

At work today i was able to take the Tiger dataset and draw a map. Tiger comes with only line data, ie. only one dimensional. However for each chain of points there are attributes referring to adjacent polygons. Using tigerpoly.py in the GDAL project i was able to construct the 2 dimensional polygons.

All that data was inserted into a PostgreSQL database with PostGIS installed. PostGIS and GDAL needed a couple patches. Then i wrote a Java program to grab the data using JDBC and drew it using AWT. Sure Java2D is better, but i'm not sure i need it. After all i'm just drawing lines and polygons. Sheesh.

I'm guessing all map data comes from the same source. The Census Bureau. Therefore, even Google (eventually) gets their data from Tiger. How is it different? Well (1) the roads have width proportional to the number of lanes, (2) all the corners are rounded, and (3) their roads are labelled. Those are the major differences in appearance. As for differences in feel, don't get me started.

And on a side note, it's been so long that i almost forgot my password to my own website. Back to dinner (Otter Creek Alpine Ale).