data-storage

For the same data set, with mostly text data, how do the data (table + index) size of Postgresql compared to that of MySQL? Postgresql uses MVCC, that would suggest its data size would be bigger In this presentation, the largest blog site in Japan talked about their migration from Postgresql to MySQL. One of their reasons for moving away from Postgresql was that data size in Postgresql was too large (p. 41): Migrating from PostgreSQL to MySQL at Cocolog, Japan's Largest Blog Community Postgresql has data compression, so that should make the data size smaller. But MySQL Plugin also has

I have an idea for how to solve this problem, but I wanted to know if there's something easier and more extensible to my problem. The program I'm working on has two basic forms of data: images, and the information associated with those images. The information associated with the images has been previously stored in a JET database of extreme simplicity (four tables) which turned out to be both slow and incomplete in the stored fields. We're moving to a new implementation of data storage. Given the simplicity of the data structures involved, I was thinking that a database was overkill. Each

I have created an sql database using Java, I am a noob when it comes to sql but have it configured and set up, i have a table created which has two columns, the first being a big integer which increments, the second I have tried defining it as a char, varchar and binary but im still not getting the desired function, say i try and store 0a a hex number into the char column i get an error, i appended 0x to the beginning a it seems to store, but when i print out the contents it is blank or in some cases i get characters such as '/' or '?', I also tried using sql explorer and it gives me the same

What is a good method to retain a small piece of data across multiple calls of a PHP script, in such a way that any call of the script can access and modify its value - no matter who calls the script? I mean something similar to $_SESSION variable, except session is strictly per-client; one client can't access another client's session. This one would be the same, no matter who accesses it. Losing the value or having it corrupted (e.g. through race conditions of two scripts launched at once) is not a big problem - if it reads correctly 90% of the time it's satisfactory. OTOH, while I know I

I'm looking for a javascript library that will let me store data in a client side database and in the back ground automatically sync the database back to the server's database preferable something that supports a variaty of engines in the same way jStore for jQuery does Looking around I can find anything Store.js deal with the client-side storage very well. Note that it supports IE6+ along with other browsers. For the server-side storage you might as well make your own script for that as it should not be difficult. Sam Dutton Since this question was asked, there's been a lot of work done on

I often hear about eventual consistency in different speeches about NoSQL, data grids etc. It seems that definition of eventual consistency varies in many sources (and maybe even depends on a concrete data storage). Can anyone give a simple explanation what Eventual Consistency is in general terms, not related to any concrete data storage? Eventual consistency: I watch the weather report and learn that it's going to rain tomorrow. I tell you that it's going to rain tomorrow. Your neighbor tells his wife that it's going to be sunny tomorrow. You tell your neighbor that it is going to rain