Skip to content
This repository has been archived by the owner on Nov 8, 2019. It is now read-only.

Migrate db to Sqlite #10

Open
smgt opened this issue Oct 13, 2011 · 4 comments
Open

Migrate db to Sqlite #10

smgt opened this issue Oct 13, 2011 · 4 comments
Assignees
Labels

Comments

@smgt
Copy link
Collaborator

smgt commented Oct 13, 2011

Migrate db to sqlite on development and use postgres on heroku. Use the gem sequel.

Schema:

Sessions:
id - session id
day - start time date YYYY-MM-DD
start - unix timestamp with start time
stop - unix timestamp with stop time
comment - session comment

Day:
day - day id YYYY-MM-DD
work - seconds worked

Settings:
key - id
value - key value

@smgt
Copy link
Collaborator Author

smgt commented Oct 13, 2011

What do you think @qzio? Couch? Mongo?

@qzio
Copy link
Owner

qzio commented Oct 25, 2011

sqlite is small and easy.

couch, mongo and redis doesn't only require a gem, it also require another daemon to run on the system eating the precious RAM.

but hmm... heruko is nice, they doesn't support files, right? mongo would be easy and nice maybe, does it cost extra? how much? :)

@smgt
Copy link
Collaborator Author

smgt commented Oct 25, 2011

Then sqlite it is!

On 25 okt 2011, at 20:23, joel hansson wrote:

sqlite is small and easy.

couch, mongo and redis doesn't only require a gem, it also require another daemon to run on the system eating the precious RAM.

Reply to this email directly or view it on GitHub:
#10 (comment)

@smgt
Copy link
Collaborator Author

smgt commented Nov 13, 2011

Checked up on heroku. We can use sqlite in development. But when you push to heroku you can use postgres instead. It's automagic.

@ghost ghost assigned smgt Nov 13, 2011
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants