[source storage] refactor source sql generation and results handling to allow repository side callbacks for instance with the BytesFileSystemStorage, before this change: * fspath, _fsopen function were stored procedures executed on the database -> files had to be available both on the repository *and* the database host * we needed implementation for each handled database Now, those function are python callbacks executed when necessary on the repository side, on data comming from the database. The litle cons are: * you can't do anymore restriction on mapped attributes * you can't write queries which will return in the same rset column some mapped attributes (or not mapped the same way) / some not This seems much acceptable since: * it's much more easy to handle when you start having the db on another host than the repo * BFSS works seemlessly on any backend now * you don't bother that much about the cons (at least in the bfss case): you usually don't do any restriction on Bytes... Bonus points: BFSS is more efficient (no queries under the cover as it was done in the registered procedure) and we have a much nicer/efficient fspath implementation. IMO, that rocks :D

     1

CubicWeb semantic web framework

     2

===============================

     3

     4

Install

     5

-------

     6

     7

More details at http://www.cubicweb.org/doc/en/admin/setup

     8

     9

Getting started

    10

---------------

    11

    12

Execute:

    13

    14

 apt-get install cubicweb cubicweb-dev cubicweb-blog

    15

 cubicweb-ctl create blog myblog

    16

 cubicweb-ctl start -D myblog

    17

 sensible-browser http://localhost:8080/

    18

    19

Details at http://www.cubicweb.org/doc/en/intro/tutorial/blog-in-five-minutes

    20

    21

Documentation

    22

-------------

    23

    24

Look in the doc/ subdirectory or read http://www.cubicweb.org/doc/en/

    25

    26

    27