max(), sum(), next()

Mensanator mensanator at aol.com
Mon Sep 8 02:49:17 CEST 2008


On Sep 7, 2:17�pm, Dennis Lee Bieber <wlfr... at ix.netcom.com> wrote:
> On Sun, 7 Sep 2008 10:30:09 -0700 (PDT), Mensanator <mensana... at aol.com>
> declaimed the following in comp.lang.python:
>
> > On Sep 6, 11:05?pm, Steven D'Aprano <st... at REMOVE-THIS-
> > cybersource.com.au> wrote:
>
> > > Sheesh. That's not a problem, because Python is not trying to be a
> > > dialect of SQL.
>
> > And yet, they added a Sqlite3 module.
>
> � � � � Which is an interface TO an embedded/stand-alone SQL-based RDBM
> engine; it does not turn Python into a dialect of SQL -- Python does not
> process the SQL, it gets passed to the engine for SQL data processing.

But that's only half the story. The other half is data returned
as a result of SQL queries. And that's something Python DOES process.
And sometimes that processed data has to be inserted back into the
database. We certainly don't want Python to process the data in a way
that the database doesn't expect.

When I see a potential flaw (such as summing an empty list to 0),
should I just keep quiet about it, or let everyone know?

Well, now they know, so I'll shut up about this from now on, ok?

> --
> � � � � Wulfraed � � � �Dennis Lee Bieber � � � � � � � KD6MOG
> � � � � wlfr... at ix.netcom.com � � � � � � wulfr... at bestiaria.com
> � � � � � � � � HTTP://wlfraed.home.netcom.com/
> � � � � (Bestiaria Support Staff: � � � � � � � web-a... at bestiaria.com)
> � � � � � � � � HTTP://www.bestiaria.com/




More information about the Python-list mailing list