A tricks I use when adding new table to backend, since I don't want to turn
migration on over production system is to create an dummy app call
generate_sql for instance... When I add new table in my main app, I copy
the web2py model defined in the models file in the dummy app, access the
app for on
If the code that reads AppConfig can't handle whitespace then this bug
should definitely be fixed!
This type of bug can be very difficult to find because it is so esoteric.
On Sunday, February 5, 2017 at 12:26:51 AM UTC-8, Ben Lawrence wrote:
>
> ok, my dumbness
> the AppConfig module doesn't lik
ok, my dumbness
the AppConfig module doesn't like '=' not aligned so instead of this
; db configuration
[db]
uri= postgres://x:x/
migrate= 1
pool_size = 10
I had this
[db]
uri = postgres://x:x/
migrate= 1
pool_size = 10
and that is why as I understa
Hopefully this is solved, but a simple test is to use the original
appconfig.ini with storage.sqlite as the connection string.
That will tell you if it is a syntax problem, at least.
-Mark
On Monday, December 26, 2016 at 7:08:23 PM UTC-6, Ben Lawrence wrote:
>
> seems to be an appconfig probl
seems to be an appconfig problem. if I don't use appconfig.ini and place
the info in db.py, everything works.
On Friday, December 23, 2016 at 6:16:12 AM UTC-8, Ben Lawrence wrote:
>
> Andre, did you solve this? For me pg 9.5 on remote ubuntu 16, web2py is
> not creating the tables.
>
> On Sunday
Andre, did you solve this? For me pg 9.5 on remote ubuntu 16, web2py is not
creating the tables.
On Sunday, September 4, 2016 at 6:55:54 AM UTC-7, Morganti wrote:
>
> Hi people!
>
> I just almost in go-live. So, I tried to create a Postgresql database and
> starting to configure some config tabl
it's one of the two: either migrations are turned off, or are turned on and
you have .table files in the databases/ folder (that tell web2py "hey,
tables are already there!")
On Monday, September 5, 2016 at 11:04:42 PM UTC+2, Morganti wrote:
>
> Hi,
>
> I checked an the migrations are enabled! I
Hi,
I checked an the migrations are enabled! I dont know where is the problem.
I checked to try to create the tables directly in postgresql and it is
running normal. But, using web2py...
Thanks
Em segunda-feira, 5 de setembro de 2016 13:11:04 UTC-3, Niphlod escreveu:
>
> appadmin shows the tab
appadmin shows the tables you DEFINED in the model.
If there aren't real table on the backend to "sustain" those models, you
get the error.
You need to let web2py create the tables in your fresh database (enable
migrations, hit appadmin at least once, then disable migrations for
production use
Hi!
In appadmin the tables are there but, checking in pgadmin3 them aren´t
there. Looks like they were not being created. But, the database is created
and I am able to create tables directly in pgadmin even prompt from ubuntu.
I reinstall everything and got the problem again.
Thank you very m
seemingly no response was given to a simple "how many records are there".
sure the tables have been created ?
On Sunday, September 4, 2016 at 3:55:54 PM UTC+2, Morganti wrote:
>
> Hi people!
>
> I just almost in go-live. So, I tried to create a Postgresql database and
> starting to configure som
11 matches
Mail list logo
