On 14/11/2010 11:15 AM, Sayth Renshaw wrote:
>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.
This concerns me as date time searching is one of the main searches I
will be performing. Any suggestions for an alternative to Sqlite,
networking supports is not important and why I had initially opted for
SQlite.
Either Postgresql or Mysql should do all you need and are easily
installable and manageable on most operating systems. You can disable
their network access easily if it is not already disabled by default.
Since you originally stated that this will eventually be part of a
larger program, Postgresql or Mysql may be the better way to start anyway.
Either way I would still have an integer auto increment primary key and
put a unique index across the date & time columns to get what you want.
Cheers,
Gary.
--
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.
