?

Log in

No account? Create an account
SFBA peeps! - Edward O'Connor [entries|archive|friends|userinfo]
Edward O'Connor

[ website | My Website ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Links
[Links:| Blog Tumblelog Lifestream ]

SFBA peeps! [Sep. 3rd, 2008|03:01 pm]
Edward O'Connor
[Feeling |expectant]

Yo.

I'll be up that-a-way this weekend, for DjangoCon. Getting in tomorrow, and planning an SF get-together with whomever wants to come.

Where
Phoenix Irish Bar
When
Tomorrow (Thursday) night, around 9

I hope to see you there!

LinkReply

Comments:
[User Picture]From: radtea
2008-09-04 12:29 am (UTC)

Serendipity


SQL is a crappy language for humans to use in dealing with complex models, so I have a little XML-based language that I use to generate SQL to create the schemas I need. Unfortunately, I have a quite different little XML-based language for generating Python to represent classes, and am now in a position where I want to bring them together, including generated code to serialize stuff in/out of the database. My usual class framework for XML serialization isn't remotely right for this, and I was just this morning trying to figure out the optimal way of dealing with this problem.

Django might be it! A quick read over the model docs and it looks like generating Django-compliant Python for the model classes will be a minor addition to my SQL generator, and the framework does all the work relative to the database that my XML framework does relative to files.

Sweet.
(Reply) (Thread)
[User Picture]From: hober
2008-09-04 06:41 pm (UTC)

Re: Serendipity

Nice! Yeah, the SQL that Django's model code generates is surprisingly efficient too.
(Reply) (Parent) (Thread)
[User Picture]From: radtea
2008-09-05 02:54 am (UTC)

Re: Serendipity

My experience so far has been very good. Ran through the first tutorial, then did some fiddling to get BLOBs into PostgreSQL, which has lame BLOB support, requiring some silly escaping of binary strings that is hideously explained in the docs.

But Django has all the right hooks to automate the process in a new Field class, so I can just treat binary data as binary data in Python, throw it at the database and forget about it.

The next fun thing is that this project is partly IBM funded, so there is DBII in my future, and Django doesn't have a native DBII backend, but after Postgres that doesn't look too bad.

I'm very impressed with the docs, and the whole thing behaves remarkably well.
(Reply) (Parent) (Thread)