How would I pass variables to a SQLAlchemy ORM definition at runtime?

Question

I've defined a new Column type called File, which should let me store only the file name in the database. Then I would store the actual file in the file system at root+subfolder+name.

File(root, subfolder="", max_length=100,  **kwargs)

The problem I'm having is that I'd like to define the root in a PasteDeploy config file. How do I define this at runtime so I can access the configuration?

score 4 · Answer 1 · answered Sep 01 '12 at 03:05

Why not avoid the complexity of a custom column type and just store the file path as a column and provide some property or hybrid property that can load the file data for you?

class Data(Base):
    path = Column(String)

def myview(request):
    data = Data(path='foo')

    root_path = request.registry.settings['data_root']
    with open(os.path.join(root_path, data.path), 'rb') as fp:
        file_data = fp.read()
    # ...

Obviously you could wrap some of that functionality into a method on Data if you wanted.

Anyway the way to access INI settings is one of the following:

during application startup from the settings/config objects.
during a request you can pass the setting in from request.registry.settings.
during a request you can access the active request via pyramid.threadlocal.get_current_request() and from there you can get the settings.

score 3 · Accepted Answer · answered Sep 01 '12 at 03:22

3

To me this sounds like your schema needs some more thought. Even if you implement a custom column type, that type still has to be mapped into SQL column types that your engine supports. For folder and filename, this is most naturally two varchar columns. So why not just use two fields, path and filename, both of type String(256) in your class?

As for the configurable root, this sounds like you want to specify the path relative to this root, so that you can change it only in one place. Having most of your configuration in the database, except for one thing which is stored in a config file, to me is a code smell. I would consider it preferable over that to have the root be a column in some other configuration table, and use a ForeignKey to refer to the root that way.

answered Sep 01 '12 at 03:22

wberry

18,519
8
53
85

Thanks for this explanation, I couldn't figure out the right way to configure the database schema. This will make things more usable outside of the Pyramid deployment. – GhotiPhud Sep 01 '12 at 03:53
In pyramid, it is customary to have all deployment related configuration in the INI file. That's not a code smell. Imagine if you want to replicate the production environment into a development server. Firstly, you do a backup / restore of the database. Next, you copy over the root folder where all the files are stored. Finally, you modify the dev INI file with the locations of the database and the root folder. Done. No need for SQL UPDATE. – sayap Sep 03 '12 at 03:18

How would I pass variables to a SQLAlchemy ORM definition at runtime?

2 Answers2