In article 82372457-2503-4682-96b3-37540328b...@w39g2000prb.googlegroups.com,
5lvqbw...@sneakemail.com wrote:
I have Section 4.4.1 of SICP rattling around in my head (database
queries), and I'm trying to come up with a simple dictionary-based
database in Python to represent circuit diagrams. My
On Dec 30 2008, 3:25 pm, 5lvqbw...@sneakemail.com wrote:
In a typical SQL database, when you type in SELECT foo FROM bar WHERE
baz='bo', you are not writing a program, at least not in the sense of
Python or C or Java or Perl where you give instructions on HOW to run
the program. You are
I have Section 4.4.1 of SICP rattling around in my head (database
queries), and I'm trying to come up with a simple dictionary-based
database in Python to represent circuit diagrams. My main confusion
isn't one of implementation, but a matter of big thinking,
fundamentally, about the problem.
On Dec 30, 12:35 pm, 5lvqbw...@sneakemail.com wrote:
I have Section 4.4.1 of SICP rattling around in my head (database
queries), and I'm trying to come up with a simple dictionary-based
database in Python to represent circuit diagrams. My main confusion
isn't one of implementation, but a
library, as I'm looking to learn to fish, so to speak, and to learn a
bit about the biology of fish.
I'm going to break rule #1 of your requirements but in an unexpected
way. Rather than studying PostgreSQL, MySQL, or Oracle, why don't you
crack open the topic of relational database theory
