Respect $db_prefix setting when working with database objects
esteewhy - September 2, 2009 - 10:45
| Project: | User Import |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Trying to import user file complains that "user_import_import_id_seq relation doesn't exist". In fact, the problem is caused by the fact that inside user_import.module file on line 1228 this sequence is called directly without obeying db_prefix semantics.
The fix is to surround sequence name with a curly brackets.
| Attachment | Size |
|---|---|
| user_import.module.patch | 539 bytes |
#1
The db_prefix semantics are for tables, do we need to wrap user_import_import_id_seq with {} ?
#2
Committed in 5.x-2.10 and 6.x-2.2 - needs testing.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.