Mono, gcj, java, c++, what?

[Eric Chadbourne]

>> I don't see how it's any harder than normal.  Last year I worked for a=

>> company that had tens of thousands of lines of code in pl/sql and it
>> worked fine.  Simple language too.  Easy for the tech support team to
>> troubleshoot.
>=20
> OK.  And when tech support tweaks the script, how do you do a diff to
> see what's changed so you can duplicate it during an upgrade?  When
> things don't work, how do you know what the last tech support person di=
d
> to their scripts?

There's a change control process.  Tech support nerd isn't allowed to
alter the code on production.  At the weekly bug meeting he can present
the issue to the developers.  Being as it's written in a simple language
he can do a lot of the investigation for the dev.  Fix must also be
QA'd.  Dev has final say on the change and checks it into source control.=


You can just view your package, procedure or function in your favorite
editor and diff as usual.  You can also connect to your control database
and check if any code is different as well.  PL/SQL Developer has the
ability to do this.  I'm sure other editors / IDE's do as well.

I'm still in the beginning stages of learning my way around postgre so
I'm not sure but I assume it's similar.

> Why not go whole hog and store all of it in the database?  Have a singl=
e
> script in front that does the C in MVC and tells the DB what content to=

> extract.

Not sure.

Thanks,
Eric C - the one who is more of a basic script writer than a 'real'
programmer.