On Friday 16 September 2005 17:51, Russell Howe wrote:
> Kern Sibbald wrote:
> > However, given some of the recent discussions, I'm not 100% what is the
> > best. I suspect that forgetting about the FileId key, something like:
> >
> > index JobId
> > index JobId, FilenameId, PathId
> >
> > would work the best for both databases (SQLite too).
>
> I wouldn't think light of dropping the primary key constraint (and
> inherent index, on all RDBMSs I know of) on the *Id attributes. You
> really don't want the possibility of two entries with the same (say)
> FileId in the File table, surely?
Yes, I was not very clear. When I wrote "forgetting about the FileId key" I
meant, "leaving the FileId key unchanged".
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
