Home/ Questions/Q 904803
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T16:06:42+00:00

Make things as simple as possible, but no simpler. Can we find the solution/s

  • 0

“Make things as simple as possible, but no simpler.“

Can we find the solution/s that fix the Python database world?

Update: A ‘lustdb’ prototype has been written by Alex Martelli – if you know any somewhat lightweight, high-level database libraries with multiple backends we could wrap in syntax sugar honey, please weigh in! 

from someAmazingDB import *  
#we imported a smart model class and db object which talk to database adapter/s
class Task (model): 
    title = ''
    done = False #native types not a custom object we have to think about!

db.taskList = []
#or
db.taskList = expandableTypeCollection(Task) #not sure what this syntax would be

db['taskList'].append(Task(title='Beat old sql interfaces',done=False))
db.taskList.append(Task('Illustrate different syntax modes',True)) # ok maybe we should just use kwargs

#at this point it should be autosaved to a default db option

#by default we should be able to reload the console and access the default db:

>> from someAmazingDB import *
>> print 'Done tasks:'
>> for task in db.taskList:
>>     if task.done:
>>         print task.title
'Illustrate different syntax modes'

I’m a fan of Python, webPy and Cherry Py, and KISS in general.

We’re talking automatic Python to SQL type translation or NoSQL.
We don’t have to totally be SQL compatible! Just a scalable subset or ignore it!

Re:model changes, it’s ok to ask the developer when they try to change it or have a set of sensible defaults.

Here is the challenge: The above code should work with very little modification or thinking required. Why must we put up with compromise when we know better?

It’s 2010, we should be able to code scalable, simple databases in our sleep.

If you think this is important, please upvote!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’ve been busy, here it is, released under LGPL:
    http://github.com/lukestanley/lustdb

    It uses JSON as it’s backend at the moment.

    This is not the same codebase Alex Martelli did.
    I wanted to make the code more readable and reusable with different
    backends and such.

    Elsewhere I have been working on object oriented HTML elements
    accessable in Python in similar ways, AND a library for making web.py
    more minimalist.

    I’m thinking of ways of using all 3 elements together with automatic
    MVC prototype construction or smart mapping.

    While old fashioned text based template web programming will be around
    for a while still because of legacy systems and because it doesn’t
    require any particular library or implementation, I feel soon we’ll
    have a lot more efficent ways of building robust, prototype friendly
    web apps.

    Please see the mailing list for those interested.

    • 0