Support #1346
closedError when run blog example with postgres backend
0%
Description
sql error
Files
Updated by Jake Petroules over 12 years ago
Could you please provide more information on exactly what errors you are receiving?
Updated by Marcio Sales over 12 years ago
- File wt_blog_error.png wt_blog_error.png added
look at the image
Updated by Koen Deforche over 12 years ago
- Status changed from New to InProgress
- Assignee set to Koen Deforche
Hey,
Indeed, it seems that .id is used but that is not a column in table user ? Could you confirm ?
So it could be that it is inadvertently hardcoded somewhere (it is always available in sqlite)...
Regards
koen
Updated by Marcio Sales over 12 years ago
no confirm. in table user have id column, but when I run sql select * from user in postgres appears a result of a system table
you must add the schema, sql following example
select u.id, u.version, u.name, u.password, u.password_method,
u.password_salt, u.role, u.failed_login_attempts, u.last_login_attempt,
u.oauth_id, u.oauth_provider from adempiere.user u join token t on u.id = t.user_id
Updated by Koen Deforche over 12 years ago
Hey,
Aah, so "user" is a really an unlucky table name. It means that we must add more explicit support for schema's instead of the current half-baked support.
Regards,
koen
Updated by Marcio Sales about 12 years ago
resolved, add the schema to mapping classes
change on BlogSession.C
mapClass("comment");
mapClass("post");
mapClass("tag");
mapClass("token");
mapClass("user");
to
mapClass("adempiere.comment");
mapClass("adempiere.post");
mapClass("adempiere.tag");
mapClass("adempiere.token");
mapClass("adempiere.user");
Updated by Koen Deforche about 12 years ago
- Status changed from InProgress to Resolved
Updated by Koen Deforche about 12 years ago
- Status changed from Resolved to Closed
- Target version set to 3.2.3
Fixed in Wt 3.2.3 RC1.