#2041: test.cfg has become the default configuration file over dev.cfg
------------------------+---------------------------------------------------
 Reporter:  kvdb        |       Owner:  faide     
     Type:  defect      |      Status:  new       
 Priority:  normal      |   Milestone:  1.1 beta 2
Component:  TurboGears  |     Version:  1.1 HEAD  
 Severity:  normal      |    Keywords:            
------------------------+---------------------------------------------------
 If I start a project using the quickstart generated ./start-project.py and
 there's no test.cfg in that directory. It picks up dev.cfg, where a MySQL
 database is configured. And that works fine.

 Now when I also have test.cfg present, that has the default SQLite
 database configured, and I ./start-project.py (without parameters, just
 like the description above), I get errors on database accesses like:

 {{{
   File "/home/kvdb/ivy/env/ivy_tg1.1_r5706/lib/python2.5/site-
 packages/SQLAlchemy-0.5.0rc4-py2.5.egg/sqlalchemy/engine/base.py", line
 909, in _handle_dbapi_exception
     raise exc.DBAPIError.instance(statement, parameters, e,
 connection_invalidated=is_disconnect)
 OperationalError: (OperationalError) no such table: item u'SELECT count(1)
 AS count_1 \nFROM item \nWHERE item.active = ?' [1]
 }}}

 When I replace the SQLite connectionstring in test.cfg with the MySQL one,
 things work fine again. Strange, because ./start-project.py should not
 pickup test.cfg by default.

 I use TG1.1 r5706.

-- 
Ticket URL: <http://trac.turbogears.org/ticket/2041>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to