Re: Usability, MySQL, Postgresql.org, gborg, contrib, etc.

I'm a great fan of Java. Still, I firmly believe that pgsql should be the
language of choice as the one included by default. I think many users
consider the ability to write functions and triggers using SQL intermixed
with the DDL statements (create function etc.) as the only natural way of
doing it. All other languages implies either mixing languages in the same
file or splitting declaration and implementation into separate files.

Java is excellent when you want to extend the language beyond what's
possible using SQL. Examples might include soundex or image recognition
algorithms. XML is another area where server side Java might play a
significant role. But that's all beyond core server functionality.

If anything, I'd rather see the JDBC and ODBC drivers reinstated in the
release. More than 56% of the PostgreSQL users (according to the poll) uses
JDBC today. ODBC is merely 18% but that might change significantly when the
native Win32 port is released. I might have missed something altogether
here, my apologies if that's the case, but looking at the coming 7.5
release, 75% of the users will be forced to download stuff from more than
one location just to get their basic stuff running.

Kind regards,

Thomas Hallgren

""scott.marlowe"" <scott(dot)marlowe(at)ihs(dot)com> wrote in message
news:Pine(dot)LNX(dot)4(dot)33(dot)0404271149070(dot)5967-100000(at)css120(dot)ihs(dot)com(dot)(dot)(dot)
> On Tue, 27 Apr 2004, Jochem van Dieten wrote:
>
> > pgsql(at)mohawksoft(dot)com wrote:
> > > (5) Programming languages. We need to make a programming language
standard
> > > in PostgreSQL. plpgsql is good, but isn't someone working on a Java
> > > language. That would be pretty slick.
> >
> > IMHO SQL/PSM would be the obvious choice for the standard
> > procedural language. Not only because it is part of the SQL
> > standard (ISO/IEC 9075-4:2003), but also because it is reasonably
> > intuitive and it is the same as what is implemented in DB2 (and
> > in MySQL 5 due sometime not so soon).
> > The only problem is that there is no PostgreSQL implementation.
>
> While I can see heading in that direction, the lack of an implementation
> makes this suggestion impractical. It will take time not just to
> implement it, but to test it and debug it, and for it to reach "maturity."
>
> PL/pgsql is mature and tested, has a great deal of code already written
> for it, and has reached maturity. I'd say including it by default
> represents little or no security risk, and increases the value, out of the
> box, of postgresql for most folks while costing very little in terms of
> wasted disk space etc...
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>