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

Database #30

Closed
arb opened this issue Oct 19, 2014 · 2 comments
Closed

Database #30

arb opened this issue Oct 19, 2014 · 2 comments
Labels
Milestone

Comments

@arb
Copy link
Contributor

arb commented Oct 19, 2014

What are we doing with the DB? Currently, we aren't doing anything with it and it's just adding complexity. We should either:

  1. Use the DB completely and even store image information in there
  2. Cut the DB out entirely for version 1

@nvcexploder can you weigh in on this?

@arb arb added the question label Oct 19, 2014
@arb arb added this to the 1.0.0 milestone Oct 19, 2014
@jaw187
Copy link
Contributor

jaw187 commented Oct 19, 2014

Cut it out.
On Oct 19, 2014 3:26 PM, "Adam Bretz" notifications@github.com wrote:

What are we doing with the DB? Currently, we aren't doing anything with it
and it's just adding complexity. We should either:

  1. Use the DB completely and even store image information in there
  2. Cut the DB out entirely for version 1


Reply to this email directly or view it on GitHub
#30.

@nvcexploder
Copy link
Contributor

agreed.

On Sun, Oct 19, 2014 at 12:59 PM, James Weston notifications@github.com
wrote:

Cut it out.
On Oct 19, 2014 3:26 PM, "Adam Bretz" notifications@github.com wrote:

What are we doing with the DB? Currently, we aren't doing anything with it
and it's just adding complexity. We should either:

  1. Use the DB completely and even store image information in there
  2. Cut the DB out entirely for version 1


Reply to this email directly or view it on GitHub
#30.


Reply to this email directly or view it on GitHub
#30 (comment).

@arb arb closed this as completed Oct 19, 2014
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

3 participants