mirror of
https://github.com/postgres/postgres.git
synced 2025-07-27 12:41:57 +03:00
* to_char:
- full support for IW (ISO week) and vice versa conversion for IW too (the to_char 'week' support is now complete and I hope correct). Thomas, I use for IW code from timestamp.c, for this I create separate function date2isoweek() from original 'case DTK_WEEK:' code in the timestamp_part(). I mean will better use one code for same feature in date_part() and in to_char(). The isoweek2date() is added to timestamp.c too. Right? IMHO in 7.1 will all to_char's features complete. It is cca 41 templates for date/time and cca 21 for numbers. * to_ascii: - gcc, is it correct now? :-) In the patch is documentation for to_char's IW and for to_ascii(). Karel
This commit is contained in:
@ -355,6 +355,12 @@
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>to_ascii(text [,name|int])</entry>
|
||||
<entry>text</entry>
|
||||
<entry>convert text from multibyte encoding to ASCII</entry>
|
||||
<entry>to_ascii('Karel')</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>char(text)</entry>
|
||||
<entry>char</entry>
|
||||
@ -447,6 +453,9 @@
|
||||
<para>
|
||||
Most functions explicitly defined for text will work for char() and varchar() arguments.
|
||||
</para>
|
||||
<para>
|
||||
The to_ascii() support conversion from LATIN1, LATIN2, WIN1250 (CP1250) only.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1>
|
||||
@ -803,6 +812,10 @@
|
||||
<entry>WW</entry>
|
||||
<entry>week number of year (1-53) where first week start on the first day of the year</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>IW</entry>
|
||||
<entry>ISO week number of year</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>CC</entry>
|
||||
<entry>century (2 digits)</entry>
|
||||
|
Reference in New Issue
Block a user