On 10/8/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote: > Jorge Vargas wrote: > > On 10/8/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote: > >> Jorge Vargas wrote: > >>> On 10/8/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote: > >>>> I have decided to not use SqlObject [1]. > >>>> > >>>> What the project should possibly do: > >>>> > >>>> * Create a new mailinglist (e.g. on Google Groups), thus the > >>>> spam-problem is reduced. The new groups should of course still be > >>>> available with the nntp interface (gmane). This step enables > >>>> _communication_ around SQLObject. (SQLAlchemy has recently moved to > >>>> google groups and I assume the would assist this project with this step). > >>>> > >>> I agree with that googlegroups is great at filtering spam. > >> ok > >> > >>>> * The remaining developers should focus to provide an sqlobject API > >>>> compatibility layer for SQLAlchemy. This way existent software can > >>>> migrate without many effort. I am sure that some projects would provide > >>>> support for this (SQLAlchemy itself, TurboGears). > >>>> > >>> I don't see why > >>> #1 SQLObject2 will provide much of the stuff SA currently does. > >> SQLObject2 is even more inactive: > >> > >> http://www.webwareforpython.org/archives/message/20060223.053837.bacf323d.en.html > >> > >> http://sqlobject.org/2/ > >> > > then get the code and start working on it. > > why? > > to backup you statement "#1 SQLObject2 will provide much of the stuff SA > currently does." ? > > No need, I'll choose another product, where contribution makes sense. > then don't complain and leave. I don't see what's the idea of complaining and not doing anything to help. > >>> #2 this "layer" already exists and it's call active mapper which is in SA > >>> trunk. > >> I don't think it's API compatible with SQLObject. > >> > > it's goal is to emulate SO-like interfaces. of course it can't be 100% > > because the underlaying layer is not SO > > So, some developers with SQLObject knowledge could possibly contribute, > would make the situation better. > why? have you even seen active mapper? it's as closest as it can be.
> >> But of course developers could contribute to this, too. > >> > >>>> * The project should move away from sourceforge. Trac provides nice > >>>> functionality for small to medium scale open source projects. > >>>> > >>> yes and you need to host it. I don't see why sf is so bad, I use trac > >>> for my stuff but that's me. > >> I (and many other's, including the python foundation) seem to see them. > >> > > then provide a trac for SO, I don't see why trac is so important vrs > > SF, it's a matter of taste. > > consistency and coherency. > huh? if they like SF then let them. > >>>> * At a minimum, the project should inform potential users about the low > >>>> activity on the SQLObject project. > >>>> > >>> Honestly I don't see why SO is "low activity" at the moment all the > >>> features it's supposed to have are there and working. > >> An ORM for a dynamic language without schema evolution support? > >> > > actually who doesn't supports dynamic language schema evolution is the > > underlaying DBs, on the other hard SO can add and remove cols at > > runtime, it is not the best thing I have to admit but it's there. > > > > I seems to me that you only know SO from it's integration to TG, and > > at that point your right from TG perspective the only way to change > > the db schema is tg-admin sql drop && tg-admin sql create. > > SQLObject does not support schema evolution (the underlying databases do). > > There's really no need to twist the facts. > I know see why people don't like you. Are you saying SO is bad because it doesn't has X or Y feature. if that the case I guess all your "reviews" are bad > >> Additionally, please review the statements of some team members within > >> this thread: > >> > >> http://thread.gmane.org/gmane.comp.python.sqlobject/6910/focus=6910 > >> > > that is what you get went a project has more people using it then > > maintaining it. > > Or when not providing the right motivation to maintain it. > or because it was not written to do that and people want it to be therefore summiting bad patches and going mad because "those bastards don't like my code" > >>>> The project lead should of course support all this moves. > >>>> > >>> man... I just wasted my time, take a look at > >>> http://en.wikipedia.org/wiki/Ilias_Lazaridis > >> I see. > >> > > and looking at the TG thread it seems you made quite a reputation on > > the django list. > > http://case.lazaridis.com/wiki/DjangoAudit > dude you got banned from the list. I think you should take that out of your "resume" > >> Hopefully the project-lead makes the right steps to save the (ptential) > >> userbase from future trouble. > >> > > I don't want to know what that means > > As suggested, the project lead should shutdown this project (or at least > place a visible remark on the website), thus other people to not loose > time in evaluating an non-maintained solution. I'm sorry but who are you to suggest that kind of thing? I have never seen you post on this list and you come in as if you have authority to anything. SO is a great tool at what it was made to do, and that is make ORM a no brainer with nice flexibility, now today people want to push non Object Oriented Relational tables into ORM and they expect it to work? I mean do your stuff and do it right. ORM are not easy ways to access a database, it's a whole diferent thing. now if (and i'm sure your thinking of this) SA is great at doing that then let it be it's goal is to provide a nice mapper pattern in which you tell your object where to pull it's data. Which for a pure Object - DB abstraction is not the best aprroach. SO serves a purpose that SA can't fill in that's why they are 2 approaches to the same problem. Projects like TG are moving to SA not because SO is bad or not maintained, is because SA is more flexible to the TG userbase. and if you "wasted your time evaluating this" then why your replying to my emails? > > Removed spam Do you spam with every message you send out? > _______________________________________________ > sqlobject-discuss mailing list > sqlobject-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
