I fully agree a bad database design can impact you for the life of the application. If this is a class assignment and the instructor gave you this as a problem then I can understand "I cannot change it" otherwise fix it now or pay forever.
*Jim Dodgen* On Wed, May 21, 2014 at 11:27 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 21 May 2014, at 7:20pm, Petite Abeille <petite.abei...@gmail.com> > wrote: > > > On May 21, 2014, at 6:00 PM, Humblebee <fantasia.d...@gmail.com> wrote: > > > >> only problem is that in this situation, the tables have already been > defined and made by someone > >> else so I cannot change it. I'm a bit stuck with the way it is. > > > > Nah… it’s software… you can always change it… in fact, better fix it > now… as there is really no reasonable way forward with your current setup… > > If you need the original data intact write a conversion routine you can > run at any time. It should read the 'personIDs' field for each team and > use it to write data into a new table. Then you can use this new table in > as many queries as you want. > > The code which depends on the existing tables doesn't need to know about > the new table so your 'someone else' shouldn't care. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
