Hallo Richard,
I use rname to be able to make use of Postgresqll schemas.
e.g. rname = 'level1.journal'
In this case when migrate is true, DAL will create a table 'journal' in
the schema 'level1' . And that is working as expected. My problem as
stated above is only when I then make changes
Hello Johann,
Do you get any advice?
I am in the process to test the rname feature and I don't find much
information, it's seems highly experimental and undocumented...
Except maybe this :
https://groups.google.com/d/msg/web2py/_q5qcARON4E/6JLCHM3eQHAJ
Richard
On Tue, Apr 1, 2014 at 4:41
I am not sure what rname does...
Does it do, what it means, so it should contains the real name of the
backend table name for instance or the reverse...
I make a test with one of my model, adding rname to the model for the table
name and one of the table field and try to make a query and look at
This is exactly what happen...
Let say I have a table like this one in Postgres :
# Postgres
CREATE TABLE address
(
id serial NOT NULL,
door_number character varying,
street character varying,
city_id integer,
CONSTRAINT address_pkey PRIMARY KEY (id )
)
WITH (
OIDS=FALSE
);
ALTER
Database: Postgresql
I get this regularly when I modify a table's definition (tables using
rname):
ProgrammingError: relation org_unit does not exist
I either set 'migrate = False' or drop the table, delete the entry in
databases and do it over - that is when the table is empty.
I suspect it
5 matches
Mail list logo
