Massimo, I know that we've talked about this in the past, but here we go again...
I'm using the latest web2py, in my applications, I would define tables as usual only to get an SQL error saying the table exists. I tried clearing out my "databases" folder, and the only way to clear out would be to delete the database entirely (which is something that I *should not* have to do). According to web2py docs, the DAL handles this type of crap perfectly and just fine. As it should, leave the migration/DAL issues to DAL and not to the user. This is what turned my head towards web2py over Django. Is CREATE TABLE `tablename` IF NOT EXISTS SQL ANSI? Either way, the MySQL handler should perform this rather than just create table under the next patch. It would solve *a lot* of hassle. The problem occurred AFTER I changed my user/pass combo for the MySQL connection string. Could this cause any problems? Someone else had this problem unresolved a long time ago... http://groups.google.com/group/web2py/browse_thread/thread/94a7107c688ad0ef/e244cc0bade80e94?hl=en&lnk=gst&q=auth+user+migrate%3Dfalse#e244cc0bade80e94 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
