On Mon, Oct 19, 2009 at 5:03 PM, John Handelaar wrote:
>
> Hello
>
> For reasons I won't bore you with, a Mysql legacy DB *whose schema I
> cannot alter* contains (inter alia) two tables. I'm trying to write
> an alternative front-end to this DB in Django which would be
> read-only.
>
> tableone
On Mon, Oct 19, 2009 at 8:03 PM, John Handelaar wrote:
>
> Hello
>
> For reasons I won't bore you with, a Mysql legacy DB *whose schema I
> cannot alter* contains (inter alia) two tables. I'm trying to write
> an alternative front-end to this DB in Django which would be
> read-only.
>
> tableone
Hello
For reasons I won't bore you with, a Mysql legacy DB *whose schema I
cannot alter* contains (inter alia) two tables. I'm trying to write
an alternative front-end to this DB in Django which would be
read-only.
tableone has a primary key called tableone_id
tabletwo contains rows which have
3 matches
Mail list logo