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 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
