Re: Storing a chain
От | Tim Clarke |
---|---|
Тема | Re: Storing a chain |
Дата | |
Msg-id | 44D9FC40FD695B4E85F1C59965C27E0F079D7F@man3.free2.local обсуждение исходный текст |
Ответ на | Storing a chain (Johan Fredrik Øhman <johanfo@ohman.no>) |
Список | pgsql-general |
The sequence isn't the order! The order is the "previous record", "next record" fields in each record... Tim Clarke -----Original Message----- From: Johan Fredrik Øhman [mailto:johanfo@ohman.no] Sent: 19 November 2003 16:50 To: 'Bruno Wolff III' Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Storing a chain I wouldn't think using a sequence would make much sense. You don't want automatically generated unique values, you want to impose an order. If you want easy insertion at the expense of larger indexes you are probably better off using a text or numeric (using digits to the right of the decimal point) key. [JFO] My use of the word sequence was ambiguous. What I ment was a "numeric" key. Why do you want your rules in a database? I would think that a plain text file would be a better approach unless you either want to be able to ask questions about your firewall rules or have some automated system for changing the firewall rules based on contidions (e.g. time of day). [JFO] Exactly, I need it very flexible. The tables are a small part of a large administration database, which tell a lot of machines exactly what firewall configuration they should have. ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
В списке pgsql-general по дате отправления: