I wasn't referring to projects written in both languages. I was
referring to projects written primarily for MySQL or "real" databases
(i.e. oracle, pgsql, mssql, db2, and on and on). No matter what
language is used, I think you'll find that apps written primarily for
mysql have poorer code than the ones written primarily for other apps.
The ones that are truly transportable will generally be the best, but if
they try to support MySQL AND the other real databases, you'll likely
find lots of hacks in the code to keep MySQL happy, that wouldn't be
needed if they didn't support it.
Does that make more sense?
On Thu, 2007-02-22 at 13:36, Mark Walker wrote:
> Hmm, I've never heard of an application that's written in both php and
> Java. However, I know of many applications that run on both mysql and
> postgresql. For instance phpbb which is the most common MB software is
> written in php and runs with either postgresql or mysql. Database
> server independence is definitely a goal for most non custom applications.
>
> Scott Marlowe wrote:
> > On Thu, 2007-02-22 at 12:17, Mark Walker wrote:
> >
> > While I'll admit to some similarities between PHP/java and mysql/pgsql,
> > I'd say that th gulf between php and java is far less than the gulf is
> > between mysql and pgsql.
> >
> > Take a list of a hundred or so db based projects written in each
> > language. Correlate it to the db used. It's likely you'll find a
> > better correlation to the db used than the language.
> >
> >
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
