If you set fake_migrate=True you mean "my table are there, do not create
them, but make the .table files". The .table files tell web2py that the
tables are in the database. If you then fake_migrate=False and
migrate=True, web2py checks the .table and decides the tables are there
(because you said so before).
web2py cannot ask the database if the tables are there. If bases its
decision on what you say. So, leave migrate=True and fake_migrate=False (or
remove fake_migrate). and delete the databases/*.table files.
I would also make a clean database to make sure the tables are really not
there (perhaps some are and some are not. who knows?)
On Thursday, 16 August 2012 10:56:37 UTC-5, weheh wrote:
>
> Nothing changes if fake_migrate=False and db.define_table('mytable', ...
> migrate=True). What I want is 'mytable' to be built, which it isn't.
>
> On Thursday, August 16, 2012 7:58:44 PM UTC+8, Niphlod wrote:
>>
>> and this is fine because you have fake_migrate=True, so, what do you want
>> ?
>>
>> On Thursday, August 16, 2012 1:55:31 PM UTC+2, weheh wrote:
>>>
>>>
>>> The log shows that the table that's not getting created was created but
>>> with the comment "faked!" after it. Postgres inspection shows table not
>>> created.
>>>
>>>
>>> On Thursday, August 16, 2012 7:07:15 PM UTC+8, Niphlod wrote:
>>>>
>>>> just open sql.log in the databases folder and see what is going on
>>>>
>>>> On Thursday, August 16, 2012 12:12:09 PM UTC+2, weheh wrote:
>>>>>
>>>>> Bother again! There is another table that's not getting created, so
>>>>> this is still an issue.
>>>>
>>>>
--
