DB implementation?

[anthonycope]

sqlalchemy is just an ORM to make it easier to interface with the database. Do we have a preference for which db we use? There's a list here: http://docs.sqlalchemy.org/en/rel_0_8/dialects/index.html

I've never created a db before so input would be appreciated.

[luqmaan]

Go for Sqlite 3.

Also, check out Peewee before you finalize on SqlAlchemy. See which one you think can get get the job done more effectively.

[jmfield2]

I would prefer MySQL, but SQLite works pretty much the same way... There
might be a difference between using one of the two on appfog as well --
they like to make mysql a premium service lol.. but switching from sql to
sql rdbms usually is pretty much as easy as changing the DSN.

It might be easier to implement a NoSQL db like couch or mongo, too... and
I think they are supported on appfog -- just some things to check out

On Fri, Feb 22, 2013 at 7:47 AM, Luqmaan Dawoodjee <notifications@github.com

wrote:

Go for Sqlite 3.

Also, check out Peewee before you finalize on SqlAlchemy. See which one
you think can get get the job done more effectively.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-13941540.

[luqmaan]

@jmfield2 The advantage of SQLite is that for local dev you don't need to set up a MySQL server and such.

Couch is nice, but would it be a good fit for the data we are storing? As of now, we are not really storing "documents." We are just storing:

• product status (price, title, url, image, etc.)
• users (name, email, contact info, products to notify, etc.)

I think a relational DB would be a better fit for this.