o.g. wrote:
> On Dec 11, 5:18 pm, Frank van Schie <nos....TakeThisOut@please.don't> wrote:
>> ScratchMonkey wrote:
>>> "o.g." <gye....TakeThisOut@gmail.com> wrote in news:e5824301-71ec-4582-971a-
>>> 569636697....TakeThisOut@s19g2000prg.googlegroups.com:
>>>> We are using jBASE5.0.2 and Oracle 10g.
>>> Did one of Vivendi's master server maintainers wander in here?
>>> 
>> One man enters, giblets leave!
>
> sorry folks....i guess this is not the right forum for this
> subject....just ignore it....my mistake
Nope, it's not. For two reasons:
1) It's not a forum, but a newsgroup, and
2) It's alt.games.starsiege.tribes. Guess you mis-posted.
As for your query, the best I can do is commiserate with you, and look
back with 20/20 hindsight and say stuff like:
- Document any and all changes.
- Never ever call work 'done' when it's just on a system. Prepare deploy
scripts that set up the database/system. To test, wipe the dev machines,
run script, and see what falls over. Has the benefit of being an
automatic disaster recovery tool if one of the servers burns down. Also,
you ensure every machine has the same structure.
- Commit deploy scripts to a source versioning system, such as CVS or
Subversion (SVN). Keep track of changes, and easily merge the work of
two developers/locations. Also functions as change-documentation. Any
conflicts will be flagged on commit.
- Design first, implement later, if the changes are database related.
Because once you make the mistake of creating a new table with different
data but an old name, it's tough to fix both the backing DB and the
front-end completely (ie., without some nearly-dead code that's gonna
blow up in a customer's face 6 months down the line).
But then, I don't know banking systems, so meh.
--
Frank
>> Stay informed about: environment synchronization 
FAQ
Search
Profile
Private Messages
Log in/Register/Password
