Anyway a good database schema is needed for a good application. Choose carefully your database schema and in fact if you get to a good solution for storaging of data you'll probably win.
Get back to the design! El 16/03/2015 a las 20:05, Hassan Schroeder escribió: > On Mon, Mar 16, 2015 at 10:00 AM, Jason O <[email protected]> wrote: > >> I am in the process of building my first project for the company I work for >> and I am stumped as how to tackle my database information problem. > Is this a legacy DB you're stuck with, or are you trying to design > one for your app? > >> What I am dealing with is a database with a list of users and a separate >> table with a list of articles that users have written. The PEOPLE table >> includes the normal name conventions as so forth, but also a value called >> Author_ID which is derived from a government entity. >> >> The ARTICLES table has a value which lists the authors of the articles, >> normally 2-7 authors per article. Here, I am not sure if this short be an >> array or just a string. I currently have it as a string. > Is this a collection of AUTHOR_IDs, or names? > > It would probably help to gist the relevant parts of your schema. > -- -- Daniel Tordable Dasilva <email: [email protected]> -- -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/55072B0B.6030305%40danieltordable.net. For more options, visit https://groups.google.com/d/optout.
