On Mon, Aug 2, 2010 at 9:39 AM, Antoni Aloy wrote:
> My first thought would be to backup the database, then put the project
> under South control. Then create a one-to-one relation between models
> and the possible create a upgrade script.
> Then, if necessary, you could create properties in the
On Mon, Aug 2, 2010 at 2:34 PM, Steve Holden wrote:
>
> Another alternative would be to create a view of the joined tables using
> SQL CREATE VIEW, then treat the view as a table in Django. You do have
> to be careful that the view should be updatable, though.
Ah... I didn't think of views. Ha
On 8/2/2010 12:39 PM, Antoni Aloy wrote:
> 2010/8/2 Nick Arnett :
>> I'm thinking that I could get a pretty good performance improvement on a
>> couple of tables by moving their LONGTEXT columns into their own tables.
>> Just wondering if there's anybody here who has done something like that - is
>
2010/8/2 Nick Arnett :
> I'm thinking that I could get a pretty good performance improvement on a
> couple of tables by moving their LONGTEXT columns into their own tables.
> Just wondering if there's anybody here who has done something like that - is
> there a way to do this transparently to Djang
I'm thinking that I could get a pretty good performance improvement on a
couple of tables by moving their LONGTEXT columns into their own tables.
Just wondering if there's anybody here who has done something like that - is
there a way to do this transparently to Django, so I don't have to re-write
5 matches
Mail list logo
