Yeah, as I said you don't want to mix them, all of the updates will be doubled. You'll probably just get errors it'll skip past, but if new columns are added to the database, then it will add two columns. It's best to use either or. I try to make the PEQ updates as complete as possible, so that might be the better way to do it. The only problem is database changes that are made before PEQ is updated. Though, when the core code changes I usually try to update PEQ to match it.
|