Phil Longstaff <[EMAIL PROTECTED]> writes:
> There are currently 3 tables which handle things which are not objects:
>
> 1) slots
> 2) recurrences
> 3) tax table entries
>
> One thing that the slot_id field provided was an ordering of the slots
> for a specific object. For slots, the order isn't important. Is there
> a reason that that recurrences or tax table entries need to be kept in a
> specific order? If so, I can still remove the id auto-increment field
> but will need to add an ordering field so that obj_guid won't be unique
> (but will be indexed), but the pair (obj_guid,order) will be unique.
Tax Table Entries are not ordered. I DOUBT Recurrences are
ordered, either. So, no, I don't think there needs to be any
particular order.
> Phil
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
