Re: OT: sheltered little world i live in -> NODB?

I have noticed over the years that this attitude is almost entirely with
Java developers. I have not had issues .Net, Python, C, Ruby or anything
else. The most surprising is the .Net. I have been on 3 projects where the
front end is in .Net. You would think Microsoft developers would be biased
against Oracle. Nope. They liked pl/sql and database features. I work with
a bunch of very experienced C developers (many have 20-30 years
experience). They have had to hire java developers due to an increase in
web development. They complain about the java guys all the time. They are
having trouble staffing up because all java guys know are libraries and the
C guys expect you to understand pointers and what is going on underneath.
The java guys don't want to write sql. C guys roll their eyes. Java guys
want to go on the web and grab any old library they find (we have secure
data, we have to make sure the libraries are secure and will function with
everything else, plus you need to be somewhat uniform. Everyone can't just
do their own thing or this will be a big mess) and so on. One C guy has to
go in and clean up a ton of really bad java code that the client wrote and
complains about it every day. The java guys want to break up our database
into many databases by de-normalizing all the tables(since you don't want
to do joins across tables). They took functionality that works and now have
to re-write it. We have single large calculation processes that are now
part of different services. Since this is complex it is hard to make sure
everyone operates the same way across teams. So the process that worked is
now broken and the C guy I just mentioned has to fix it. We have not broken
up the database. I reminded them 'just wait until we have to commit the
same field to 5 databases. If one commit fails, then we don't have a
transaction. So then they will want to write archive and redo logs, but
probably call it something else. On the bright side, we have much smaller
databases!

On my last project, the java architect told me that views are evil and that
oracle can't handle recursive programming. I tried to explain that connect
by prior has been around 20 years, but he lost interest. This was a pretty
small database. It was about 100 gbs, but 98 gbs were in pdfs that they
stored and fetched. They complained that oracle was slow. So I turned on
auditing in the DB to capture all my sqls. Went into the app and clicked a
button. I saw 10 sqls for the first button. No wonder its slow ...


--
http://www.freelists.org/webpage/oracle-l

Other related posts: