mirror of
				https://github.com/postgres/postgres.git
				synced 2025-10-30 00:04:49 -04:00 
			
		
		
		
	Add psql TODO item:
> o Add option to wrap column values at whitespace boundaries, > rather than chopping them at a fixed width. > Currently, "wrapped" format chops values into fixed > widths. Perhaps the word wrapping could use the same > algorithm documented in the W3C specification. > http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php > http://www.w3.org/TR/CSS21/tables.html#auto-table-layout
This commit is contained in:
		
							parent
							
								
									8eee65c996
								
							
						
					
					
						commit
						c96d5df53e
					
				
							
								
								
									
										9
									
								
								doc/TODO
									
									
									
									
									
								
							
							
						
						
									
										9
									
								
								doc/TODO
									
									
									
									
									
								
							| @ -1,7 +1,7 @@ | ||||
| PostgreSQL TODO List | ||||
| ==================== | ||||
| Current maintainer:	Bruce Momjian (bruce@momjian.us) | ||||
| Last updated:		Thu Jun 26 22:38:18 EDT 2008 | ||||
| Last updated:		Mon Jun 30 15:41:25 EDT 2008 | ||||
| 
 | ||||
| The most recent version of this document can be viewed at | ||||
| http://www.postgresql.org/docs/faqs.TODO.html. | ||||
| @ -1121,7 +1121,14 @@ Clients | ||||
| 
 | ||||
| 	o -Improve display of enums to show valid enum values | ||||
| 	o Add prompt escape to display the client and server versions | ||||
| 	o Add option to wrap column values at whitespace boundaries, | ||||
|           rather than chopping them at a fixed width. | ||||
| 
 | ||||
| 	  Currently, "wrapped" format chops values into fixed | ||||
| 	  widths.  Perhaps the word wrapping could use the same | ||||
| 	  algorithm documented in the W3C specification. | ||||
| 	  http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php | ||||
| 	  http://www.w3.org/TR/CSS21/tables.html#auto-table-layout | ||||
| 
 | ||||
| * pg_dump / pg_restore | ||||
| 	o %Add dumping of comments on index columns and composite type columns | ||||
|  | ||||
| @ -8,7 +8,7 @@ | ||||
| <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> | ||||
| <h1><a name="section_1">PostgreSQL TODO List</a></h1> | ||||
| <p>Current maintainer:     Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/> | ||||
| Last updated:           Thu Jun 26 22:38:18 EDT 2008 | ||||
| Last updated:           Mon Jun 30 15:41:25 EDT 2008 | ||||
| </p> | ||||
| <p>The most recent version of this document can be viewed at<br/> | ||||
| <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. | ||||
| @ -969,6 +969,14 @@ first.  There is also a developer's wiki at<br/> | ||||
| </p> | ||||
|     </li><li>-<em>Improve display of enums to show valid enum values</em> | ||||
|     </li><li>Add prompt escape to display the client and server versions | ||||
|     </li><li>Add option to wrap column values at whitespace boundaries, | ||||
|           rather than chopping them at a fixed width. | ||||
| <p>          Currently, "wrapped" format chops values into fixed | ||||
|           widths.  Perhaps the word wrapping could use the same | ||||
|           algorithm documented in the W3C specification. | ||||
|           <a href="http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php">http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php</a> | ||||
|           <a href="http://www.w3.org/TR/CSS21/tables.html<strong>auto-table-layout">http://www.w3.org/TR/CSS21/tables.html</strong>auto-table-layout</a> | ||||
| </p> | ||||
|   </li></ul> | ||||
|   </li><li>pg_dump / pg_restore | ||||
|   <ul> | ||||
|  | ||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user