[ckan-dev] got chance to talk about webstore?

[Julian Todd]

Friedrich,

All pretty interesting.  I'll get logged in to the webstore github and post
my comments.

You guessed the purpose of jargtypes correctly; it's a temporary hack and
not supposed to be pretty.

We're trying to get a deployment on our system sooner, so we can handle some
interim ugliness.

I was struggling with the way that the "blob" type is done in sqlalchemy is
not the same as in sqlite.  Sqlite blob is untyped, so gives back float or
int if that's what you put in, and worked for our swvariables table.  Can't
do this through sqlalchemy.

I'll file my comments into the github comments so they can be reviewed.

The main proposal is I'd like to break down that save(unique_keys=[],
data={}) function into its constituent parts and potentially implement it in
the client.

Julian.


It would be good to get that save(unique_keys=[], data={}) command out of
the webstore completely.  It doesn't really belong.  We should consider
doing it in the client if possible, and making it literally a compound
function.

1) create if not exists or extend table columns if not complete (jargtypes =
{ key=>type })

2) create if not exists index( unique keys
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20111003/466bd3b8/attachment-0002.html>