Submitted: http://code.google.com/p/web2py/issues/detail?id=1126
-Jim
On Tuesday, October 30, 2012 1:29:43 PM UTC-5, Massimo Di Pierro wrote:
>
> Please open a ticket about this. I will fix it in the next couple of days.
>
> On Tuesday, 30 October 2012 10:00:28 UTC-5, Jim S wrote:
>>
>> It seems
Please open a ticket about this. I will fix it in the next couple of days.
On Tuesday, 30 October 2012 10:00:28 UTC-5, Jim S wrote:
>
> It seems then like it converts everything to lower case in the .table file
> if you create it from scratch but if you run a fake_migrate then it doesn't
> conve
It seems then like it converts everything to lower case in the .table file
if you create it from scratch but if you run a fake_migrate then it doesn't
convert to lower case. Just appears (on the surface) that it is
inconsistent behavior. I've been a camel-case guy since my powerbuilder
days b
this is a question for Massimo, although ... we know your test is on
ubuntu, but your production is on linux too ?
PS: I see a comment like this in DAL
# make sure all field names are lower case to avoid
# migrations because of case cahnge
so it's likely that those differencies won't trigger a m
Ok, now adding on to this situation.
In my db.py I have the following defined:
district = db.define_table('district',
Field('districtId', 'id', readable=False),
Field('district', length=5, required=True, unique=True),
Field('districtNumber', 'integer', required=True,
unique=True, label='District
yep, that can cause troubles.
table files are named with an hash composed with the uri string, so you can
import, let's say, table definitions for 10 dbs all in the same folder.
If table files were created with an uri, and you try to auto_import with
another uri, web2py will "search" for the "w
Found it. I had inconsistent case specified in my database name. When
running in web2py it was infoCenter2, when running outside, I had
infocenter2. Changing to infoCenter2 caused it to work correctly.
Niphlod - Thanks for all the help. I truly appreciate it.
-Jim
On Tue, Oct 23, 2012 at 4:4
Ok, I've got it now to where there are files in the databases directory,
but still getting empty list for print db.tables
-Jim
On Tue, Oct 23, 2012 at 4:21 PM, Niphlod wrote:
> auto_import scans the table files for tables. That's the whole point of
> not redefining models (because they are stor
auto_import scans the table files for tables. That's the whole point of not
redefining models (because they are stored in table files that can be read).
Normal behaviour is:
DAL(..., migrate=True)
let it define tables, then
DAL(, migrate=False) #or migrate_enabled=False
so table files are never to
It is empty.
On Tue, Oct 23, 2012 at 4:01 PM, Niphlod wrote:
> is your databases folder filled with the .table files relative to the
> tables ?
>
>
> On Tuesday, October 23, 2012 10:57:04 PM UTC+2, Jim S wrote:
>>
>> Hi - I use MySQL for my database. In my production environment I'm
>> specifyi
is your databases folder filled with the .table files relative to the
tables ?
On Tuesday, October 23, 2012 10:57:04 PM UTC+2, Jim S wrote:
>
> Hi - I use MySQL for my database. In my production environment I'm
> specifying the following:
>
> db = DAL(infoCenterUtil.getDalString(), migrate=Fals
11 matches
Mail list logo
