Rails4 support, PostgreSQL array and hstore fields support

[turgu1]

This is an update to support Rails4 (using the modification proposed by edwardvalentini in his own fork) and the use of array fields and hstore fields as supplied by PostgreSQL.

The Rails4 modification may render yaml_db unusable with older versions of rails (this needs to be verified). The PostgreSQL support changes are compatible with other kind of database systems. That doesn't mean it supply support for array and hstore fields for other database systems...

Cheers!

Guy

[amir20]

Can this be merged? I see that it works.

[turgu1]

Good Day Amir,

I'm using it since a month almost every day now. Sure it can be merged. I don't really now how to do it.

Guy

Email: turgu666@gmail.com

On Sep 23, 2013, at 13:42, Amir Raminfar notifications@github.com wrote:

Can this be merged? I see that it works.

—
Reply to this email directly or view it on GitHub.

[turgu1]

Sorry for this close / reopen toggling. I'm not familiar with the way github is working...

[dnrce]

What is the use case for supporting functionality that's specific to PostgreSQL? If you're locked to PG, doesn't that mean you can just use pg_dump and don't have any need for yaml_db?

[jrgifford]

Having a cross-host, low-barrier data system has been nice for us at work (I'm using this patch). Yes, we could (and did) do zipped sql blobs - but then we couldn't put it into version control. Being able to go back to different database snapshots using yamldb has been very useful.