Modify ↓
#3270 closed defect (worksforme)
trac-admin initenv with postgresql is failed when system locale is EUC-KR
| Reported by: | Owned by: | Christian Boos | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | admin/console | Version: | 0.9.5 |
| Severity: | normal | Keywords: | postgresql |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Hi.
My linux(Gentoo) box's default locale is ko_KR.EUC-KR. I emerged postgresql(8.1.2), created data directory and initialized database unerder EUC-KR.
The error occured when trac-admin try insert default data to database. I tried it many times, but same result.
So, I changed system default locale to UTF-8, recreated data directory and initialized new database under UTF-8. Then, I run trac-admin and it's initialize process is successed.
Is it bug or my misunderstanding?
Attachments (0)
Change History (6)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
Ok. It's no problem.
- My System Infomation
OS : Gentoo Linux (Kernel 2.6.16-gentoo-r7) CPU : Intel Pentium4 Postgresql (emerged) : 8.1.4 Trac (emerged) : 0.9.5 Python (emerged) : 2.4.2 Psycopg (emerged) : 1.1.18
- Error Message (include trac-admin message)
=========================== BEGIN ============================
architect ~ #trac-admin /data/www/localhost/trac/tractest2 initenv
Creating a new Trac environment at /data/www/localhost/trac/tractest2
Trac will first ask a few questions about your environment
in order to initalize and prepare the project database.
Please enter the name of your project.
This name will be used in page titles and descriptions.
Project Name [My Project]> EUC-KR Tect Project
Please specify the connection string for the database to use.
By default, a local SQLite database is created in the environment
directory. It is also possible to use an already existing
PostgreSQL database (check the Trac documentation for the exact
connection string syntax).
Database connection string [sqlite:db/trac.db]> postgres://testuser:testpwd@localhost/EUCKR_DB
Please specify the absolute path to the project Subversion repository.
Repository must be local, and trac-admin requires read+write
permission to initialize the Trac database.
Path to repository [/var/svn/test]> /data/svn/testsvn
Please enter location of Trac page templates.
Default is the location of the site-wide templates installed with Trac.
Templates directory [/usr/share/trac/templates]>
Creating and Initializing Project
Configuring Project
trac.repository_dir
trac.database
trac.templates_dir
project.name
Installing default wiki pages
/usr/share/trac/wiki-default/TracReports => TracReports
Failed to initialize environment. ??: "EUC_KR" ????? ??? ? ?? ??? ??: 0xe280
INSERT INTO wiki(version,name,time,author,ipnr,text) SELECT 1+COALESCE(max(version),0),'TracReports',1150418176, 'trac','127.0.0.1','= Trac Reports =
[[TracGuideToc]]
The Trac reports module provides a simple, yet powerful reporting facility
to present information about tickets in the Trac database.
Rather than have its own report definition format, TracReports relies on standard SQL
`SELECT` statements for custom report definition.
''''''Note:'''''' ''''The report module is being phased out in its current form because it seriously limits the ability of the Trac team to make adjustments to the underlying database schema. We believe that the [wiki:TracQuery query module] is a good replacement that provides more flexibility and better usability. While there are certain reports that cannot yet be handled by the query module, we intend to further enhance it so that at some point the reports module can be completely removed. This also means that there will be no major enhancements to the report module anymore.''''
''''You can already completely replace the reports module by the query module simply be disabling the former in [wiki:TracIni trac.ini]:''''
{{{
[components]
trac.ticket.report.* = disabled
}}}
''''This will make the query module the default handler for the a€œView Ticketsa€
A report consists of these basic parts:
* ''''''ID'''''' -- Unique (sequential) identifier
* ''''''Title'''''' -- Descriptive title
* ''''''Description'''''' -- A brief description of the report, in WikiFormatting text.
* ''''''Report Body'''''' -- List of results from report query, formatted according to the methods described below.
* ''''''Footer'''''' -- Links to alternative download formats for this report.
== Changing Sort Order ==
Simple reports - ungrouped reports to be specific - can be changed to be sorted by any column simply by clicking the column header.
If a column header is a hyperlink (red), click the column you would like to sort by. Clicking the same header again reverses the order.
== Alternate Download Formats ==
Aside from the default HTML view, reports can also be exported in a number of alternate formats.
At the bottom of the report page, you will find a list of available data formats. Click the desired link to
download the alternate report format.
=== Comma-delimited - CSV (Comma Separated Values) ===
Export the report as plain text, each row on its own line, columns separated by a single comma ('','').
''''''Note:'''''' Carriage returns, line feeds, and commas are stripped from column data to preserve the CSV structure.
=== Tab-delimited ===
Like above, but uses tabs (\\t) instead of comma.
=== RSS - XML Content Syndication ===
All reports support syndication using XML/RSS 2.0. To subscribe to an RSS feed, click the orange ''XML'' icon at the bottom of the page. See TracRss for general information on RSS support in Trac.
----
== Creating Custom Reports ==
''''Creating a custom report requires a comfortable knowledge of SQL.''''
A report is basically a single named SQL query, executed and presented by
Trac. Reports can be viewed and created from a custom SQL expression directly
in from the web interface.
Typically, a report consists of a SELECT-expression from the ''ticket'' table,
using the available columns and sorting the way you want it.
== Ticket columns ==
The ''''ticket'''' table has the following columns:
* id
* time
* changetime
* component
* severity
* priority
* owner
* reporter
* cc
* version
* milestone
* status
* resolution
* summary
* description
See TracTickets for a detailed description of the column fields.
''''''all active tickets, sorted by priority and time''''''
''''''Example:'''''' ''''All active tickets, sorted by priority and time''''
{{{
SELECT id AS ticket, status, severity, priority, owner,
time as created, summary FROM ticket
WHERE status IN (''new'', ''assigned'', ''reopened'')
ORDER BY priority, time
}}}
----
== Advanced Reports: Dynamic Variables ==
For more flexible reports, Trac supports the use of ''''dynamic variables'''' in report SQL statements.
In short, dynamic variables are ''''special'''' strings that are replaced by custom data before query execution.
=== Using Variables in a Query ===
The syntax for dynamic variables is simple, any upper case word beginning with ''$'' is considered a variable.
Example:
{{{
SELECT id AS ticket,summary FROM ticket WHERE priority=''$PRIORITY''
}}}
To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the the leading ''$''.
Example:
{{{
http://projects.edgewall.com/trac/reports/14?PRIORITY=high
}}}
To use multiple variables, separate them with an ''&''.
Example:
{{{
http://projects.edgewall.com/trac/reports/14?PRIORITY=high&SEVERITY=critical
}}}
=== Special/Constant Variables ===
There is one ''''magic'''' dynamic variable to allow practical reports, its value automatically set without having to change the URL.
* $USER -- Username of logged in user.
Example (''''List all tickets assigned to me''''):
{{{
SELECT id AS ticket,summary FROM ticket WHERE owner=''$USER''
}}}
----
== Advanced Reports: Custom Formatting ==
Trac is also capable of more advanced reports, including custom layouts,
result grouping and user-defined CSS styles. To create such reports, we''ll use
specialized SQL statements to control the output of the Trac report engine.
== Special Columns ==
To format reports, TracReports looks for ''magic'' column names in the query
result. These ''magic'' names are processed and affect the layout and style of the
final report.
=== Automatically formatted columns ===
* ''''''ticket'''''' -- Ticket ID number. Becomes a hyperlink to that ticket.
* ''''''created, modified, date, time'''''' -- Format cell as a date and/or time.
* ''''''description'''''' -- Ticket description field, parsed through the wiki engine.
''''''Example:''''''
{{{
SELECT id as ticket, created, status, summary FROM ticket
}}}
=== Custom formatting columns ===
Columns whose names begin and end with 2 underscores (Example: ''''''_''''''''''''_color_''''''''''''_'''''') are
assumed to be ''''formatting hints'''', affecting the appearance of the row.
* ''''''_''''''''''''_group_''''''''''''_'''''' -- Group results based on values in this column. Each group will have its own header and table.
* ''''''_''''''''''''_color_''''''''''''_'''''' -- Should be a numeric value ranging from 1 to 5 to select a pre-defined row color. Typically used to color rows by issue priority.
* ''''''_''''''''''''_style_''''''''''''_'''''' -- A custom CSS style expression to use for the current row.
''''''Example:'''''' ''''List active tickets, grouped by milestone, colored by priority''''
{{{
SELECT p.value AS __color__,
t.milestone AS __group__,
(CASE owner WHEN ''daniel'' THEN ''font-weight: bold; background: red;'' ELSE '''' END) AS __style__,
t.id AS ticket, summary
FROM ticket t,enum p
WHERE t.status IN (''new'', ''assigned'', ''reopened'')
AND p.name=t.priority AND p.type=''priority''
ORDER BY t.milestone, p.value, t.severity, t.time
}}}
''''''Note:'''''' A table join is used to match ''''ticket'''' priorities with their
numeric representation from the ''''enum'''' table.
=== Changing layout of report rows ===
By default, all columns on each row are display on a single row in the HTML
report, possibly formatted according to the descriptions above. However, it''s
also possible to create multi-line report entries.
* ''''''column_'''''' -- ''''Break row after this''''. By appending an underscore (''_'') to the column name, the remaining columns will be be continued on a second line.
* ''''''_column_'''''' -- ''''Full row''''. By adding an underscore (''_'') both at the beginning and the end of a column name, the data will be shown on a separate row.
* ''''''_column'''''' -- ''''Hide data''''. Prepending an underscore (''_'') to a column name instructs Trac to hide the contents from the HTML output. This is useful for information to be visible only if downloaded in other formats (like CSV or RSS/XML).
''''''Example:'''''' ''''List active tickets, grouped by milestone, colored by priority, with description and multi-line layout''''
{{{
SELECT p.value AS __color__,
t.milestone AS __group__,
(CASE owner
WHEN ''daniel'' THEN ''font-weight: bold; background: red;''
ELSE '''' END) AS __style__,
t.id AS ticket, summary AS summary_, -- ## Break line here
component,version, severity, milestone, status, owner,
time AS created, changetime AS modified, -- ## Dates are formatted
description AS _description_, -- ## Uses a full row
changetime AS _changetime, reporter AS _reporter -- ## Hidden from HTML output
FROM ticket t,enum p
WHERE t.status IN (''new'', ''assigned'', ''reopened'')
AND p.name=t.priority AND p.type=''priority''
ORDER BY t.milestone, p.value, t.severity, t.time
}}}
=== Reporting on custom fields ===
If you have added custom fields to your tickets (experimental feature in v0.8, see TracTicketsCustomFields), you can write a SQL query to cover them. You''ll need to make a join on the ticket_custom table, but this isn''t especially easy.
If you have tickets in the database ''''before'''' you declare the extra fields in trac.ini, there will be no associated data in the ticket_custom table. To get around this, use SQL''s "LEFT OUTER JOIN" clauses. See TracIniReportCustomFieldSample for some examples.
----
See also: TracTickets, TracQuery, TracGuide' FROM wiki WHERE name='TracReports'
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/trac/scripts/admin.py", line 612, in do_initenv
self._do_wiki_load(default_dir('wiki'), cursor)
File "/usr/lib/python2.4/site-packages/trac/scripts/admin.py", line 790, in _do_wiki_load
self._do_wiki_import(filename, page, cursor)
File "/usr/lib/python2.4/site-packages/trac/scripts/admin.py", line 760, in _do_wiki_import
cursor, (title, int(time.time()), data, title))
File "/usr/lib/python2.4/site-packages/trac/scripts/admin.py", line 177, in db_update
cursor.execute(sql, params)
ProgrammingError: ??: "EUC_KR" ????? ??? ? ?? ??? ??: 0xe280
INSERT INTO wiki(version,name,time,author,ipnr,text) SELECT 1+COALESCE(max(version),0),'TracReports',1150418176, 'trac','127.0.0.1','= Trac Reports =
[[TracGuideToc]]
The Trac reports module provides a simple, yet powerful reporting facility
to present information about tickets in the Trac database.
Rather than have its own report definition format, TracReports relies on standard SQL
`SELECT` statements for custom report definition.
''''''Note:'''''' ''''The report module is being phased out in its current form because it seriously limits the ability of the Trac team to make adjustments to the underlying database schema. We believe that the [wiki:TracQuery query module] is a good replacement that provides more flexibility and better usability. While there are certain reports that cannot yet be handled by the query module, we intend to further enhance it so that at some point the reports module can be completely removed. This also means that there will be no major enhancements to the report module anymore.''''
''''You can already completely replace the reports module by the query module simply be disabling the former in [wiki:TracIni trac.ini]:''''
{{{
[components]
trac.ticket.report.* = disabled
}}}
''''This will make the query module the default handler for the a€œView Ticketsa€
A report consists of these basic parts:
* ''''''ID'''''' -- Unique (sequential) identifier
* ''''''Title'''''' -- Descriptive title
* ''''''Description'''''' -- A brief description of the report, in WikiFormatting text.
* ''''''Report Body'''''' -- List of results from report query, formatted according to the methods described below.
* ''''''Footer'''''' -- Links to alternative download formats for this report.
== Changing Sort Order ==
Simple reports - ungrouped reports to be specific - can be changed to be sorted by any column simply by clicking the column header.
If a column header is a hyperlink (red), click the column you would like to sort by. Clicking the same header again reverses the order.
== Alternate Download Formats ==
Aside from the default HTML view, reports can also be exported in a number of alternate formats.
At the bottom of the report page, you will find a list of available data formats. Click the desired link to
download the alternate report format.
=== Comma-delimited - CSV (Comma Separated Values) ===
Export the report as plain text, each row on its own line, columns separated by a single comma ('','').
''''''Note:'''''' Carriage returns, line feeds, and commas are stripped from column data to preserve the CSV structure.
=== Tab-delimited ===
Like above, but uses tabs (\\t) instead of comma.
=== RSS - XML Content Syndication ===
All reports support syndication using XML/RSS 2.0. To subscribe to an RSS feed, click the orange ''XML'' icon at the bottom of the page. See TracRss for general information on RSS support in Trac.
----
== Creating Custom Reports ==
''''Creating a custom report requires a comfortable knowledge of SQL.''''
A report is basically a single named SQL query, executed and presented by
Trac. Reports can be viewed and created from a custom SQL expression directly
in from the web interface.
Typically, a report consists of a SELECT-expression from the ''ticket'' table,
using the available columns and sorting the way you want it.
== Ticket columns ==
The ''''ticket'''' table has the following columns:
* id
* time
* changetime
* component
* severity
* priority
* owner
* reporter
* cc
* version
* milestone
* status
* resolution
* summary
* description
See TracTickets for a detailed description of the column fields.
''''''all active tickets, sorted by priority and time''''''
''''''Example:'''''' ''''All active tickets, sorted by priority and time''''
{{{
SELECT id AS ticket, status, severity, priority, owner,
time as created, summary FROM ticket
WHERE status IN (''new'', ''assigned'', ''reopened'')
ORDER BY priority, time
}}}
----
== Advanced Reports: Dynamic Variables ==
For more flexible reports, Trac supports the use of ''''dynamic variables'''' in report SQL statements.
In short, dynamic variables are ''''special'''' strings that are replaced by custom data before query execution.
=== Using Variables in a Query ===
The syntax for dynamic variables is simple, any upper case word beginning with ''$'' is considered a variable.
Example:
{{{
SELECT id AS ticket,summary FROM ticket WHERE priority=''$PRIORITY''
}}}
To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the the leading ''$''.
Example:
{{{
http://projects.edgewall.com/trac/reports/14?PRIORITY=high
}}}
To use multiple variables, separate them with an ''&''.
Example:
{{{
http://projects.edgewall.com/trac/reports/14?PRIORITY=high&SEVERITY=critical
}}}
=== Special/Constant Variables ===
There is one ''''magic'''' dynamic variable to allow practical reports, its value automatically set without having to change the URL.
* $USER -- Username of logged in user.
Example (''''List all tickets assigned to me''''):
{{{
SELECT id AS ticket,summary FROM ticket WHERE owner=''$USER''
}}}
----
== Advanced Reports: Custom Formatting ==
Trac is also capable of more advanced reports, including custom layouts,
result grouping and user-defined CSS styles. To create such reports, we''ll use
specialized SQL statements to control the output of the Trac report engine.
== Special Columns ==
To format reports, TracReports looks for ''magic'' column names in the query
result. These ''magic'' names are processed and affect the layout and style of the
final report.
=== Automatically formatted columns ===
* ''''''ticket'''''' -- Ticket ID number. Becomes a hyperlink to that ticket.
* ''''''created, modified, date, time'''''' -- Format cell as a date and/or time.
* ''''''description'''''' -- Ticket description field, parsed through the wiki engine.
''''''Example:''''''
{{{
SELECT id as ticket, created, status, summary FROM ticket
}}}
=== Custom formatting columns ===
Columns whose names begin and end with 2 underscores (Example: ''''''_''''''''''''_color_''''''''''''_'''''') are
assumed to be ''''formatting hints'''', affecting the appearance of the row.
* ''''''_''''''''''''_group_''''''''''''_'''''' -- Group results based on values in this column. Each group will have its own header and table.
* ''''''_''''''''''''_color_''''''''''''_'''''' -- Should be a numeric value ranging from 1 to 5 to select a pre-defined row color. Typically used to color rows by issue priority.
* ''''''_''''''''''''_style_''''''''''''_'''''' -- A custom CSS style expression to use for the current row.
''''''Example:'''''' ''''List active tickets, grouped by milestone, colored by priority''''
{{{
SELECT p.value AS __color__,
t.milestone AS __group__,
(CASE owner WHEN ''daniel'' THEN ''font-weight: bold; background: red;'' ELSE '''' END) AS __style__,
t.id AS ticket, summary
FROM ticket t,enum p
WHERE t.status IN (''new'', ''assigned'', ''reopened'')
AND p.name=t.priority AND p.type=''priority''
ORDER BY t.milestone, p.value, t.severity, t.time
}}}
''''''Note:'''''' A table join is used to match ''''ticket'''' priorities with their
numeric representation from the ''''enum'''' table.
=== Changing layout of report rows ===
By default, all columns on each row are display on a single row in the HTML
report, possibly formatted according to the descriptions above. However, it''s
also possible to create multi-line report entries.
* ''''''column_'''''' -- ''''Break row after this''''. By appending an underscore (''_'') to the column name, the remaining columns will be be continued on a second line.
* ''''''_column_'''''' -- ''''Full row''''. By adding an underscore (''_'') both at the beginning and the end of a column name, the data will be shown on a separate row.
* ''''''_column'''''' -- ''''Hide data''''. Prepending an underscore (''_'') to a column name instructs Trac to hide the contents from the HTML output. This is useful for information to be visible only if downloaded in other formats (like CSV or RSS/XML).
''''''Example:'''''' ''''List active tickets, grouped by milestone, colored by priority, with description and multi-line layout''''
{{{
SELECT p.value AS __color__,
t.milestone AS __group__,
(CASE owner
WHEN ''daniel'' THEN ''font-weight: bold; background: red;''
ELSE '''' END) AS __style__,
t.id AS ticket, summary AS summary_, -- ## Break line here
component,version, severity, milestone, status, owner,
time AS created, changetime AS modified, -- ## Dates are formatted
description AS _description_, -- ## Uses a full row
changetime AS _changetime, reporter AS _reporter -- ## Hidden from HTML output
FROM ticket t,enum p
WHERE t.status IN (''new'', ''assigned'', ''reopened'')
AND p.name=t.priority AND p.type=''priority''
ORDER BY t.milestone, p.value, t.severity, t.time
}}}
=== Reporting on custom fields ===
If you have added custom fields to your tickets (experimental feature in v0.8, see TracTicketsCustomFields), you can write a SQL query to cover them. You''ll need to make a join on the ticket_custom table, but this isn''t especially easy.
If you have tickets in the database ''''before'''' you declare the extra fields in trac.ini, there will be no associated data in the ticket_custom table. To get around this, use SQL''s "LEFT OUTER JOIN" clauses. See TracIniReportCustomFieldSample for some examples.
----
See also: TracTickets, TracQuery, TracGuide' FROM wiki WHERE name='TracReports'
architect ~ #
=========================== END ============================
comment:3 by , 18 years ago
| Keywords: | postgresql added |
|---|---|
| Milestone: | → 0.10.1 |
| Owner: | changed from to |
I think this issue depends on which bindings are used.
With pyPgSQL, a call to "set client_encoding to unicode" is probably missing, see pyPgSQL manual 2.2.5
(so it seems that r3159 was only a partial fix for #3013).
I use a database for which ENCODING = 'UTF-8', so the above is not needed, but I suspect it is when the encoding is different.
However, with Psycopg2 this seems to be not needed from a cursory inspection of the code (but I haven't tested).
Lastly, the reporter is using Psycopg1, which we said is not supported in 0.10.
comment:4 by , 18 years ago
I create the database with UTF8 encoding. Therefore my local encoding should not matter:
createdb --encoding=utf8 --owner=trac trac
comment:5 by , 16 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
I'm closing this as worksforme since I believe this is caused by using a different database encoding than utf8.
The database encoding has to be utf8. But the postgresql database cluster locale can be anything.
Please reopen this ticket if this is not the case.
Note:
See TracTickets
for help on using tickets.
Can you provide some more information? The error message and the version of the Python Postgres library you're using would be helpful to determine what's happening.