Hi Joe, On Sep 5, 2006, at 9:37 PM, Joe wrote:
> > Joe wrote: >> I'm following the tutorial and on page 2, I've hit a number of minor >> annoyances. > > They're now starting to be more than minor ... > >> 4. Tried to click on "Comment on this page" link on the bottom right >> and was taken to a New Ticket Trac page, indicating >> >> Permission Denied >> >> TICKET_CREATE privileges are required to perform this operation >> >> At that point I opted to write this email. > > Do I have to get TICKET_CREATE privileges? I only want to make some > comments and suggestions (unless I find something critical). If the > newsgroup is the preferred place to make comments, then perhaps the > link > should be changed to go to groups.google.com. Due to trac spam, we set Trac to require TICKET_CREATE. You can register right there on the page, and there's a guest account. Actually, though, the documentation is all moving to http://docs.turbogears.org/ which allows comments right on the page. Hopefully, we won't end up with a spam problem there. If we do, though, I think it can be taken care of. >> 5. I played with tg-admin help to find I should use tgadmin sql >> create >> -c dev.cfg to get it to look at the right config file. However, that >> led to another traceback ending with >> >> File >> "/usr/local/lib/python2.4/site-packages/SQLObject-0.7.1dev_r1457- >> py2.4.egg/sqlobject/dbconnection.py", >> line 924, in connectionForURI >> assert self.instanceNames.has_key(uri), \ >> AssertionError: No SQLObject driver exists under the name dev.cfg >> >> I guess I need to install a PG driver, but it's too late now so I'll >> have to research that tomorrow. However, it would also be helpful if >> the tutorial mentioned the need for the driver. > > I installed psycopg1 and followed their tutorial enough to create a > Person table without a problem, but tg-admin sql create still > complains > about no SQLObject driver. As I mentioned yesterday, my dev.cfg has > this line: > > sqlobject.dburi="postgres://[EMAIL PROTECTED]/tg" > > and I used the same string with connectionForURI() directly. In line > 316 of command.py, it's being called with self.options.connection_uri, > so I assume sqlobject.dburi somehow isn't making it down to > self.options.connection_uri, and I'm pretty sure someone will be kind > enough to tell me why that may be happening :-) Offhand, I'm not sure. Everything looks correct from what you're saying there. Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
