[Nitro] [Og] DBI adapter and Sequel

[Mark Van De Vyver]

The rake:test:og output (dbi-mysql adapter)

Running og...                                                  [  33
specs - all passed ]
Running og/adapter/dbi...                                      [  21
specs - all passed ]
Running og/adapter/dbi/create...                               [  26
specs - all passed ]
Running og/adapter/dbi/dbd/mysql...                            [   2
specs - all passed ]
Running og/adapter/dbi/dbd/sqlite...                           [   1
specs - all passed ]
Running og/adapter/dbi/override...                             [   0
specs -   0 failed ]
Running og/adapter/dbi/sequel/array_keys_spec...               [   0
specs -   0 failed ]
Running og/adapter/dbi/sequel/connection_pool...               [  24
specs - all passed ]
Running og/adapter/dbi/sequel/core_ext...                      [  35
specs - all passed ]
Running og/adapter/dbi/sequel/database...                      [ 101
specs - all passed ]
Running og/adapter/dbi/sequel/dataset...                       [ 209
specs - all passed ]
Running og/adapter/dbi/sequel/migration_spec...                [   0
specs -   0 failed ]
Running og/adapter/dbi/sequel/model...                         [   6
specs -   3 failed ]
Running og/adapter/dbi/sequel/pretty_table_spec...             [   0
specs -   0 failed ]
Running og/adapter/dbi/sequel/schema_generator_spec...         [   0
specs -   0 failed ]
Running og/adapter/dbi/sequel/schema_spec...                   [   0
specs -   0 failed ]
Running og/adapter/dbi/sequel/sequelizer...                    [  41
specs - all passed ]
Running og/adapter/dbi/utils...                                [ 435
specs - all passed ]
Running og/adapter/oracle...                                   [   0
specs -   0 failed ]
Running og/adapter/postgresql...                               [   0
specs -   0 failed ]
Running og/model...                                            [   2
specs -   1 failed ]
Running og/model/orderable...                                  [   6
specs -   3 failed ]
Running og/model/taggable...                                   [   2
specs - all passed ]
Running og/model/timestamped...                                [   2
specs -   1 failed ]
Running og/model/uuid...                                       [   0
specs -   0 failed ]
Running og/relation/has_many...                                [   2
specs -   1 failed ]
Running og/store/sql...                                        [   0
specs -   0 failed ]
Running og/store/sql/utils...                                  [   0
specs -   0 failed ]
Running og/util/ann_attr...                                    [   2
specs -   1 failed ]
Running og/validation...                                       [   2
specs - all passed ]


On Nov 20, 2007 6:27 PM, Mark Van De Vyver <mvyver at gmail.com> wrote:
> Hi Devs
> I've made some progress with the DBI adapter and incorporating some to
> Sequel's code/functionality into Og.
> By that statement I mean I've got some of my and some of Sequel's
> specs to run.
> I've not used any of this in anger - so it is best described as proof
> of concept/experimental.
>
> The question is what to do with this in light of the looming 0.50
> release main/branch.
> I'm currently using the main repo and not the branch.
>
> I've included the rake:test:og output below.
>
> Essentially I've been able to the following Sequel specs to run:
> database, dataset, sequelizer, connection_pool, core_ext
> I've made some changes to Og's settings and how options are handled in
> Og, to accommodate the DBI adapter,
> and I've written some spec's, there is also some error handling and
> documentation that might be worth plundering?
>
> The reason for wanting to submit now is that I've hit some hurdle in
> getting Sequel' Model specs to run, and it is probably worth getting
> some more talented minds looking at and discussing this.
>
> Anyway, as I said these might be considered experimental/proof of
> concept results but should be worth while looking at incorporating.
> This also raised some issues that might be worth discussing thinking about.
>
> Appreciate any suggestions.
> Mark
>