Thread: [SQLObject] SO bugs/enhancement/etc on TurboGears tracker, please take a look so we can take action
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: Jorge V. <jor...@gm...> - 2006-08-19 20:27:41
|
Hi the other day I sat down with Turbogears bug tracker and gather all relevant SQLObject bugs posted below, I'll love it if you guys could find some time to look into them. I know we can't fix them all but some seem to be very easy and others just features request, I personally don't know SO internals so I'm not sure how hard it will be to fix/implement them. So as I said we don't expect to have them all done but I do want so movement, even if that means we have to close it as wont fix, or move it to SO's bug tracker thats fine with me. for the others I'll like to clarify where the bug is, is this a SO issue or a TG issue?, for example the SOclasses related ones seem to be in sqlobject-admin which I undestand is not maintained much, so maybe we could push TG to stop using it. As i said we just want movement so even a we'll probably never implement this is a great response. Thanks in advance. original email below ----------- Hey I manage to at least organice the bugs we have this is seudo wiki so follow the = Most of them seem to be in SO but some may not, if we could clean this list up and then send it to the SO people maybe most of them will be closed. Even if it is as won't fix. = bugs = == inside Turbogears == #no attribute 'autocommit http://trac.turbogears.org/turbogears/ticket/763 #I didn't undestand this one. http://trac.turbogears.org/turbogears/ticket/817 == inside SQLObject == #SOclasses PATCH http://trac.turbogears.org/turbogears/ticket/882 #soClasses is a hack fix the real issue http://trac.turbogears.org/turbogears/ticket/279 #import classes into model http://trac.turbogears.org/turbogears/ticket/77 #issie with sockets/param strings http://trac.turbogears.org/turbogears/ticket/305 #missing data in sqlobject-admin create / sql-admin sql sql http://trac.turbogears.org/turbogears/ticket/1010 http://trac.turbogears.org/turbogears/ticket/1015 === backend specific=== #firebird http://trac.turbogears.org/turbogears/ticket/83 #No reconnect if connection is drop #mysql & postgre http://trac.turbogears.org/turbogears/ticket/872 http://trac.turbogears.org/turbogears/ticket/781 = enhancements = == inside TG == #sqlobject caching http://trac.turbogears.org/turbogears/ticket/61 SQLObject is at rev 1800+ and we are at 1457 shouldn't we upgrade before we get into the 1.0 betas? I know not all that code has been going into the 0.7bugfix but still some things have for example for example #738 was apply in sqlobject r1774 == SQLobject == #change SQLObject to use looging module. http://trac.turbogears.org/turbogears/ticket/65 #make IntermediateTables more robust add PK,UNIQUE, index http://trac.turbogears.org/turbogears/ticket/990 === Not so common use cases === #he has 2 id's and a InheritableSQLObject, and he specs them to be the same, this sounds more like a feature http://trac.turbogears.org/turbogears/ticket/583 #one table defined with one connection the other with default, and they are mixing eachother. http://trac.turbogears.org/turbogears/ticket/657 = closed = http://trac.turbogears.org/turbogears/ticket/345 http://trac.turbogears.org/turbogears/ticket/201 |
From: Oleg B. <ph...@ma...> - 2006-08-20 11:00:46
|
On Sat, Aug 19, 2006 at 04:27:33PM -0400, Jorge Vargas wrote: > I personally don't know SO internals Now it's good time to start learning! > for the others I'll like to clarify where the bug is, is this a SO > issue or a TG issue? I am afrais it is someone else's job. I am not going to install and learn TurboGears just to understand a bug report. This is a job for those who run TG and report bugs. Oleg. -- Oleg Broytmann http://phd.pp.ru/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |
From: Oleg B. <ph...@ph...> - 2006-08-24 16:34:27
|
Hello! I did look at this. On Sat, Aug 19, 2006 at 04:27:33PM -0400, Jorge Vargas wrote: > = bugs = > == inside Turbogears == > #no attribute 'autocommit > http://trac.turbogears.org/turbogears/ticket/763 Valid concern, but invalid test. I cannot run tests that requires TG. Create an SQLObject-only test and submit a bug report to the SF tracker so you can track it and add a report to the original ticket. > #I didn't undestand this one. > http://trac.turbogears.org/turbogears/ticket/817 Agagin, there is a test that requires TG. Create an SQLObject-only test and submit a bug report to the SF tracker. > == inside SQLObject == > #SOclasses PATCH > http://trac.turbogears.org/turbogears/ticket/882 The patch looks strange. What is the .__reversed__() attribute? > #soClasses is a hack fix the real issue > http://trac.turbogears.org/turbogears/ticket/279 It is already in the command.py, so what is the problem? Close the ticket. > #import classes into model > http://trac.turbogears.org/turbogears/ticket/77 It is fixed, too (sqlobject.txt), I think. Close the ticket. > #issie with sockets/param strings > http://trac.turbogears.org/turbogears/ticket/305 To specify a unix domain socket with SQLObject use the syntax: postgres:///var/run/postgresql/test?debug=1 For MySQL it is "unix_socket" argument: mysql://localhost/database?unix_socket=/var/lib/mysql/socket Close the ticket. > #missing data in sqlobject-admin create / sql-admin sql sql > http://trac.turbogears.org/turbogears/ticket/1010 Fixed in the trunk two days ago. Close the ticket. > http://trac.turbogears.org/turbogears/ticket/1015 This again about the order of creation. Close the ticket. > === backend specific=== > #firebird > http://trac.turbogears.org/turbogears/ticket/83 What is type_conv? Copy this one to the SQLObject tracker and add an explanation - what is it and of what type (None, string, int). > #No reconnect if connection is drop > #mysql & postgre > http://trac.turbogears.org/turbogears/ticket/872 > http://trac.turbogears.org/turbogears/ticket/781 Valid concern, invalid patch. The patch has been already rejected in this list. Please copy the bug report to the SF tracker. > = enhancements = > == inside TG == > #sqlobject caching > http://trac.turbogears.org/turbogears/ticket/61 No patch attached. Close the ticket. > == SQLobject == > #change SQLObject to use looging module. > http://trac.turbogears.org/turbogears/ticket/65 SQLObject still supports Python 2.2 that doesn't have logging module. No patch attached. Close the ticket. It is in our TODO anyway. > #make IntermediateTables more robust add PK,UNIQUE, index > http://trac.turbogears.org/turbogears/ticket/990 We have a similar bug reports in our tracker. Close as dup. > === Not so common use cases === > #he has 2 id's and a InheritableSQLObject, and he specs them to be the > same, this sounds more like a feature > http://trac.turbogears.org/turbogears/ticket/583 Probbaly a real bug. Create an SQLObject-only test and submit a bug report to the SF tracker. > #one table defined with one connection the other with default, and > they are mixing eachother. > http://trac.turbogears.org/turbogears/ticket/657 I am sure this is a TG problem rather than a SQLObject problem. If not - please give me a test. > = closed = > http://trac.turbogears.org/turbogears/ticket/345 > http://trac.turbogears.org/turbogears/ticket/201 They are already closed. Should I look into them? Oleg. -- Oleg Broytmann http://phd.pp.ru/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |
From: Jorge V. <jor...@gm...> - 2006-08-26 04:12:41
|
On 8/24/06, Oleg Broytmann <ph...@ph...> wrote: > Hello! I did look at this. Thank you very much I appreciate it. > > On Sat, Aug 19, 2006 at 04:27:33PM -0400, Jorge Vargas wrote: > > = bugs = > > == inside Turbogears == > > #no attribute 'autocommit > > http://trac.turbogears.org/turbogears/ticket/763 > > Valid concern, but invalid test. I cannot run tests that requires TG. > Create an SQLObject-only test and submit a bug report to the SF tracker so > you can track it and add a report to the original ticket. > this is a very weird case, we haven't been able to track down what exactly happens because it isn't in all instalations. and they are a number of diferent databases affected by it therefore we think it may be SO, but unfortunally we have no concrete non-TG cases. > > #I didn't undestand this one. > > http://trac.turbogears.org/turbogears/ticket/817 > > Agagin, there is a test that requires TG. Create an SQLObject-only test > and submit a bug report to the SF tracker. > > > == inside SQLObject == > > #SOclasses PATCH > > http://trac.turbogears.org/turbogears/ticket/882 > > The patch looks strange. What is the .__reversed__() attribute? > > > #soClasses is a hack fix the real issue > > http://trac.turbogears.org/turbogears/ticket/279 > > It is already in the command.py, so what is the problem? Close the > ticket. I dont see it at http://svn.colorstudy.com/SQLObject/branches/0.7-bugfix/sqlobject/manager/command.py > > > #import classes into model > > http://trac.turbogears.org/turbogears/ticket/77 > > It is fixed, too (sqlobject.txt), I think. Close the ticket. closed > > > #issie with sockets/param strings > > http://trac.turbogears.org/turbogears/ticket/305 > > To specify a unix domain socket with SQLObject use the syntax: > postgres:///var/run/postgresql/test?debug=1 > For MySQL it is "unix_socket" argument: > mysql://localhost/database?unix_socket=/var/lib/mysql/socket > Close the ticket. > closed and I'll make a note for documentation > > #missing data in sqlobject-admin create / sql-admin sql sql > > http://trac.turbogears.org/turbogears/ticket/1010 > > Fixed in the trunk two days ago. Close the ticket. great thanks. closed > > > http://trac.turbogears.org/turbogears/ticket/1015 > > This again about the order of creation. Close the ticket. close > > > === backend specific=== > > #firebird > > http://trac.turbogears.org/turbogears/ticket/83 > > What is type_conv? Copy this one to the SQLObject tracker and add an > explanation - what is it and of what type (None, string, int). I'll ask kevin to more it and post a better explanation. > > > #No reconnect if connection is drop > > #mysql & postgre > > http://trac.turbogears.org/turbogears/ticket/872 > > http://trac.turbogears.org/turbogears/ticket/781 > > Valid concern, invalid patch. The patch has been already rejected in > this list. Please copy the bug report to the SF tracker. posted 1547004 > > > = enhancements = > > == inside TG == > > #sqlobject caching > > http://trac.turbogears.org/turbogears/ticket/61 > > No patch attached. Close the ticket. done > > > == SQLobject == > > #change SQLObject to use looging module. > > http://trac.turbogears.org/turbogears/ticket/65 > > SQLObject still supports Python 2.2 that doesn't have logging module. > No patch attached. Close the ticket. It is in our TODO anyway. > > > #make IntermediateTables more robust add PK,UNIQUE, index > > http://trac.turbogears.org/turbogears/ticket/990 > > We have a similar bug reports in our tracker. Close as dup. which number? I want to leave a trail when I close that one. > > > === Not so common use cases === > > #he has 2 id's and a InheritableSQLObject, and he specs them to be the > > same, this sounds more like a feature > > http://trac.turbogears.org/turbogears/ticket/583 > > Probbaly a real bug. Create an SQLObject-only test and submit a bug > report to the SF tracker. > > > #one table defined with one connection the other with default, and > > they are mixing eachother. > > http://trac.turbogears.org/turbogears/ticket/657 > > I am sure this is a TG problem rather than a SQLObject problem. If not - > please give me a test. > > > = closed = > > http://trac.turbogears.org/turbogears/ticket/345 > > http://trac.turbogears.org/turbogears/ticket/201 > > They are already closed. Should I look into them? no I forgot to took those out when send this to the TG trunk list. > > Oleg. > -- > Oleg Broytmann http://phd.pp.ru/ ph...@ph... > Programmers don't die, they just GOSUB without RETURN. > |