Hi, I have to agree with Karl, this means I don't understand your issue either. As far as I see it, there are two possibilities:
1. The sequence is not connected to the data in your database is any way. In this case, you might be interested in the original definition of your sequence. And you might be interested in separately manipulating the value of the sequence. On the other hand, since your sequence has nothing to do with your data(base), you do not want to have it within the same backup. You don't backup two different databases together (I mean inseparably), do you? The script you use to create the sequence will be backup enough. And since you have this script, you can alter the value of the sequence to any value you like, afterwards. 2. The sequence is connected to the data in your database. In this case, the current value of your sequence has a meaning. The initial value of this sequence is meaningless, this value is already used by the data in your database and should not be used again. If you use a sequence to fill a column of a table, it is the value of the sequence, not the function call which is stored. Therefor, restoring the actual value of the sequence is what you want. I personally think, it is a bad idea trying to store the initial schema definition within a production or development database. I do software develpment myself, and the product I develop is used within a large data warehouse. While implementing new features, the table definitions change. Within the development, I group the table columns in order to have columns for the same kind of feature together. In the production database I add columns by using the alter table statement. So physically the new columns are stored at the end of the row. This way, I have a huge difference between the "initial state" of the database and the actual schema definition. My software doesn't mind. Ronald On 24 Feb 2006 12:42:31 +0530 Ajay Dalvi <[EMAIL PROTECTED]> wrote: > Hi Karl, > Lets say I am having one database tempdb, in that sequence > mysequence exists. > The sequence mysequence's current value is 12. > Now due to some changes that needs to be done in database tempdb, i need > to reinstall tempdb database. > Before installing new version tempdb, i need to take the data backup of > the current database, so that after installing new version I can put the > old data back into the database. > Here is the need of changing the sequence value to 12 without changing > its definition, when we put the old data back into the database. > > > -Ajay > -- independIT Integrative Technologies GmbH Sitz der Gesellschaft: Schrobenhausen HRB Neuburg B 1.521 Geschäftsführer: Dieter Stubler, Dipl. Inform. (FH) Ronald Jeninga, Diplom Mathematiker _______________________________________________ Users mailing list [email protected] http://ingres.ca.com/mailman/listinfo/users
