On Wed, Apr 29, 2009 at 10:42 AM, DavidP wrote:
>
> A solution to the schema evolution problem is to reframe it and solve
> a different problem.
While I'm glad you are enthusiastic about the schema evolution
problem, now is not the best time to be discussing it. We are trying
(desperately) to g
A solution to the schema evolution problem is to reframe it and solve
a different problem.
The "problem" with schema evolution is caused by a violation of the
DRY principle. There is redundancy between the db schema and
django's .py files. The DRY violation may be removed by coding an
applicat
On Wed, Apr 29, 2009 at 3:13 AM, Malcolm Tredinnick
wrote:
>
> On Tue, 2009-04-28 at 14:38 -0400, Nathan Auch [Sybase] wrote:
>> Hi Russ,
>>
>> Thanks for taking the time to respond. We will finish off the SQL
>> Anywhere work in Django and then follow the procedure you outlined. It
>> sounds lik
On Apr 27, 10:49 pm, Malcolm Tredinnick
wrote:
>
> Permit me to correct that impression: you are mistaken.
Good! That's what I want'ed to be.
>
> That's also not a really valid assumption. There are still significant
> differences and different limitations and advantages with each approach
>
On Tue, 2009-04-28 at 14:38 -0400, Nathan Auch [Sybase] wrote:
> Hi Russ,
>
> Thanks for taking the time to respond. We will finish off the SQL
> Anywhere work in Django and then follow the procedure you outlined. It
> sounds like starting with a externally maintained module and seeing
> where
On Tue, Apr 28, 2009 at 2:38 PM, Nathan Auch [Sybase] wrote:
>
> Hi Russ,
>
> Thanks for taking the time to respond. We will finish off the SQL
> Anywhere work in Django and then follow the procedure you outlined. It
> sounds like starting with a externally maintained module and seeing
> where tha
Hi Russ,
Thanks for taking the time to respond. We will finish off the SQL
Anywhere work in Django and then follow the procedure you outlined. It
sounds like starting with a externally maintained module and seeing
where that takes us is the way to go. I'll be reading this list going
forward s
On Tue, Apr 28, 2009 at 10:17 PM, Nathan Auch [Sybase] wrote:
>
> I'm a developer on the core engine team of the SQL Anywhere database
> server (http://www.sybase.com/products/databasemanagement/sqlanywhere).
> We're in the final stages of adding a SQL Anywhere database backend to
> Django and wo
I'm a developer on the core engine team of the SQL Anywhere database
server (http://www.sybase.com/products/databasemanagement/sqlanywhere).
We're in the final stages of adding a SQL Anywhere database backend to
Django and would like to share our work with the community. What is the
process for ge
About the initial problem that started this thread, the associated bug
number is #10948.
On Apr 6, 10:41 pm, Karen Tracey wrote:
> On Mon, Apr 6, 2009 at 1:56 PM, Marty Alchin wrote:
>
> > On Mon, Apr 6, 2009 at 1:16 PM, Karen Tracey wrote:
> > > I feel like I'm going around in circles thinki
On Mon, Apr 27, 2009 at 5:35 PM, SrRecruiter wrote:
> Python Web Developer [...]
Please direct job posts to django-users; django-dev is for discussion
of developing Django itself.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
11 matches
Mail list logo
