Re: SQL backend database scheme

Hey Jan,

A couple small nits:

* maybe use "txn_id" rather than "txt_id". the latter sounds like
"text" rather than "transaction", and "txn" is used in the APIs

* transactions_proplist has a txnprop_id which is never referenced.
I'd suggest making <txn_id, name> the primary key.

Cheers,
-g

2010/3/29 Jan Horák <horak.honza_at_gmail.com>:
> Hi everybody,
>
> I've prepared a database scheme of the upcoming MySQL backend, it is avaible
> at:
> http://www.stud.fit.vutbr.cz/~xhorak50/diplomathesis/files/100329_mysql_design_v1.png
>
> I have arisen from BDB and FSFS backend design, some previous analyses:
> http://www.stud.fit.vutbr.cz/~xhorak50/diplomathesis/files/100309_dag_structures_sql.pdf
> http://www.stud.fit.vutbr.cz/~xhorak50/diplomathesis/files/100329_backend_operations_analysis.pdf
>
> and from historic MySQL backend design:
> http://homepages.paradise.net.nz/~ejrh/subversion/mysql/
>
> Any ideas or comments will be appreciated.
>
> Jan Horak
> horak.honza_at_gmail.com
>
Received on 2010-04-01 21:02:40 CEST