On Nov 14, 4:51 pm, Sayth Renshaw <[email protected]> wrote: > > Its a very simple schema as I am only just beginning. Essentially its is a > notetaking database, which later i plan to incorporate as part of a bigger > program in Ruby. > > Schema > > ID(Randomly generated Number?) - EventDate - EventTime - Location - Event > Number - Name - General Comment - Name Comment - CommentDate/Time > > Most searching will be done by name which is unique as well. Most searching > will be done via Name.
unless you're using UUIDs to manage data that will be synchronised across multiple database instances, don't use a random ID. is the event number meant to be changeable? if not, use it as the primary key. I would tend to use a single timestamp field instead of the 2 date and time fields, though with SQLite's poor datetime handling you'd need to jump through a couple of hoops to query for events on a particular day. I guess in that case it makes sense to use distinct fields. -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
