Is it just me, or is Sqlite3 goofy?

mensanator at aol.com mensanator at aol.com
Tue Sep 12 21:28:21 CEST 2006


Fredrik Lundh wrote:
> mensanator at aol.com wrote:
>
> > Because I can extrapolate. I *know* before even trying it that
> > if I export all my data from a sqlite db to a csv file and then try
> > to import it into Access that there will be problems if the fields
> > aren't static typed.
>
> that's just the old "C++/Java is better than Smalltalk/Python/Ruby"
> crap.  we've seen it before, and it's no more true when it comes from
> you than when it comes from some Java head.  people who've actually used
> dynamic typing knows that it doesn't mean that all objects have random
> types all the time.

No, it isn't the same old crap. When I define an Access field as
Double, I cannot insert a value such as ">200" or "ND" or "Yes".
I'm not saying static typing is better, just that migrating a dynamic
types to static types may cause difficulties that wouldn't be present
if it was static to static.

And if you call the "C++/Java is better than Smalltalk/Python/Ruby"
statement crap, why do you accept the statement that
"static typing is a bug in the SQL specification"? Isn't that
crap also?

>
> > That's one of the reasons why I was such a good test engineer.
> > I could anticipate problems the design engineers didn't think of
> > and I would deliberately provoke those problems during testing
> > and crash their hardware/software.
> >
> > I wasn't very popular.
>
> no wonder, if you kept running around telling your colleagues that they
> were liars and crackpots and slanderers when things didn't work as you
> expected.

Nobody cared about that. What they cared about was my
reporting to their boss that the latest version of the software
was no better than the previous version who then had to figure
out how to explain to the customer that the improvement he
was promised didn't materialize and who then had to explain
to his boss why the customer still hadn't signed off on the
delivery and pay the bill.

> what's your current line of work, btw?

Database manager for an a geotechnical consulting firm doing
environmental remediation.

> 
> </F>




More information about the Python-list mailing list