On Tue, 22 Apr 2008 09:47:54 +0100, Robert Forkel
<[EMAIL PROTECTED]> wrote:
> On Tue, Apr 22, 2008 at 10:26 AM, Nick Murdoch <[EMAIL PROTECTED]>
> wrote:
>
>> The difference to me is that SQLAlchemy requires you to know how SQL
>> works
>> in much greater depth, /and/ to learn how SQLAlch
On Tue, Apr 22, 2008 at 10:26 AM, Nick Murdoch <[EMAIL PROTECTED]> wrote:
> The difference to me is that SQLAlchemy requires you to know how SQL works
> in much greater depth, /and/ to learn how SQLAlchemy interfaces with it
> all, before you can start using it. I'm not a DB expert, and I like
On Tue, 22 Apr 2008 03:21:26 +0100, Daniel Fetchinson
<[EMAIL PROTECTED]> wrote:
>> But have you given any thought as to positioning against SQLAlechemy?
>>
>> It's a totally appropriate answer to say that you'll just continue
>> working
>> on SQLObject and not really pay attention to what oth
On Mon, Apr 21, 2008 at 08:18:42PM -0300, Sam's Lists wrote:
> But have you given any thought as to positioning against SQLAlechemy?
I haven't. There is a number of ORMs in the Python world (SO, SA, Storm,
PyDO, Database Row, Yet Another ORM, etc.) but I don't have any idea of
their advantages
> But have you given any thought as to positioning against SQLAlechemy?
>
> It's a totally appropriate answer to say that you'll just continue working
> on SQLObject and not really pay attention to what others are doing, of
> course.
>
> But I think that if we want to continue to get new users, we
Oleg.. (and other developers)
I hope you don't mind the question
But have you given any thought as to positioning against SQLAlechemy?
It's a totally appropriate answer to say that you'll just continue working
on SQLObject and not really pay attention to what others are doing, of
course.
Bu
On Mon, Apr 21, 2008 at 08:15:54AM -0700, Daniel Fetchinson wrote:
> maybe the work is too much
> for a single person.
It is, to an extent. But anyone can help. Code, tests, documentation
- any help will be great help!
> Sometimes you hear people saying that sqlobject's
> development is slow
> Hello! The first thing I want to tell is that SQLObject is a community
> project. There are people who provide patches (sometime big patches for
> major features), there are developers who have commit access to the
> Subversion repository. I am one of those, but certainly far from being the
> onl
Hello! The first thing I want to tell is that SQLObject is a community
project. There are people who provide patches (sometime big patches for
major features), there are developers who have commit access to the
Subversion repository. I am one of those, but certainly far from being the
only one.
On
Oleg, I was searching for a document outlining the future of sqlobject
but couldn't find any so here it goes:
In the current development phase are you primarily concentrating on
bug fixes and maintenance releases?
Do you have plans for developing totally new features?
Would you be willing to devel
10 matches
Mail list logo
