11307 Commits (306798ded52cfd72e4fa7c0923c94de8b07bd739)

 

All Branches   

Search

Author	SHA1	Message	Date
Bruce Momjian	66b77dbcd6	Prompt for password from /dev/tty and fall back to stdin/stderr.	25 years ago
Tatsuo Ishii	cdce507053	Forgot to add this file...	25 years ago
Bruce Momjian	1c6bd04713	PG_DUMP NLS (Russian) ... Here is another one :) Another chunk of translated messages. Please apply to the same file. Serguei Mokhov	25 years ago
Tom Lane	8f6d72cb39	Suggest placing audit trail on pg_shadow, not its view pg_user.	25 years ago
Tatsuo Ishii	df4cba68cf	Commit Patrice's patches except: ... > - corrects a bit the UTF-8 code from Tatsuo to allow Unicode 3.1 > characters (characters with values >= 0x10000, which are encoded on > four bytes). Also, update mb/expected/unicode.out. This is necessary since the patches affetc the result of queries using UTF-8. --------------------------------------------------------------- Hi, I should have sent the patch earlier, but got delayed by other stuff. Anyway, here is the patch: - most of the functionality is only activated when MULTIBYTE is defined, - check valid UTF-8 characters, client-side only yet, and only on output, you still can send invalid UTF-8 to the server (so, it's only partly compliant to Unicode 3.1, but that's better than nothing). - formats with the correct number of columns (that's why I made it in the first place after all), but only for UNICODE. However, the code allows to plug-in routines for other encodings, as Tatsuo did for the other multibyte functions. - corrects a bit the UTF-8 code from Tatsuo to allow Unicode 3.1 characters (characters with values >= 0x10000, which are encoded on four bytes). - doesn't depend on the locale capabilities of the glibc (useful for remote telnet). I would like somebody to check it closely, as it is my first patch to pgsql. Also, I created dummy .orig files, so that the two files I created are included, I hope that's the right way. Now, a lot of functionality is NOT included here, but I will keep that for 7.3 :) That includes all string checking on the server side (which will have to be a bit more optimised ;) ), and the input checking on the client side for UTF-8, though that should not be difficult. It's just to send the strings through mbvalidate() before sending them to the server. Strong checking on UTF-8 strings is mandatory to be compliant with Unicode 3.1+ . Do I have time to look for a patch to include iso-8859-15 for 7.2 ? The euro is coming 1. january 2002 (before 7.3 !) and over 280 millions people in Europe will need the euro sign and only iso-8859-15 and iso-8859-16 have it (and unfortunately, I don't think all Unices will switch to Unicode in the meantime).... err... yes, I know that this is not every single person in Europe that uses PostgreSql, so it's not exactly 280m, but it's just a matter of time ! ;) I'll come back (on pgsql-hackers) later to ask a few questions regarding the full unicode support (normalisation, collation, regexes,...) on the server side :) Here is the patch ! Patrice. -- Patrice HÉDÉ ------------------------------- patrice à islande org ----- -- Isn't it weird how scientists can imagine all the matter of the universe exploding out of a dot smaller than the head of a pin, but they can't come up with a more evocative name for it than "The Big Bang" ? -- What would _you_ call the creation of the universe ? -- "The HORRENDOUS SPACE KABLOOIE !" - Calvin and Hobbes ------------------------------------------ http://www.islande.org/ -----	25 years ago
Tatsuo Ishii	d07bacd54a	Add UTF-8 char >= 0x10000 check	25 years ago
Tom Lane	9bc15d499d	Update examples of type coercion rules --- some of them no longer worked ... as the example claimed, because of changes elsewhere in the system.	25 years ago
Tom Lane	e3b3eb20a4	Synchronize with main parser's keyword list (someone didn't check his ... last commit very carefully...)	25 years ago
Bruce Momjian	360e61e1f5	Update FAQ.	25 years ago
Michael Meskes	1ebc028cbc	- Fixed GRANT statement. ... - Synced preproc.y with gram.y.	25 years ago
Tom Lane	e482dcb0a4	Make selectivity routines cope gracefully with NaNs, infinities, and ... NUMERIC values that are out of the range of 'double'. Per trouble report from Mike Quinn.	25 years ago
Peter Eisentraut	d1c6983899	Fix logic in insert() function.	25 years ago
Tom Lane	9ca41c0413	Fixing closed-path intersection logic causes this test to find more ... streets than it used to...	25 years ago
Tom Lane	cf5dc330b9	path_inter, path_distance, path_length, dist_ppath now do the right ... things with closed paths --- ie, include the closing line segment in their calculations. Per bug report from Curtis Barrett 9-Oct-01.	25 years ago
Tom Lane	58dc94abac	Add missing prototype to suppress gcc warning.	25 years ago
Tom Lane	f42b88d1b4	Residual cleanup from making pltcl unknown support always enabled.	25 years ago
Tom Lane	b2c37b4c51	Autoconf.	25 years ago
Bruce Momjian	657d0044b0	Update FAQ.	25 years ago
Bruce Momjian	46712990bd	More keyword uppercasing.	25 years ago
Bruce Momjian	8123d8f150	Here are few more translated messages into Russian ... for the PG_DUMP component. Please apply to </src/bin/pg_dump/ru.po> Serguei A. Mokhov	25 years ago
Bruce Momjian	1d3a47af0c	Attached patch for unconditional enabling of pltcl-unknown support. ... Enabling this feature adds very light overhead of 1 select from pg_class on first using of pl/tcl in backend if unknown suppport is really unused. But pl/tcl with this support has very improved functionality. Patch includes changes to documentation.	25 years ago
Bruce Momjian	36458b93e0	Update FAQ.	25 years ago
Bruce Momjian	db7aa99fb9	Update FAQ.	25 years ago
Bruce Momjian	dac9f40ba8	Mention createlang when language not installed, per problem report.	25 years ago
Bruce Momjian	cdd4379394	Update FAQ.	25 years ago
Bruce Momjian	0818073894	More uppercasing.	25 years ago
Bruce Momjian	705869dd17	Uppercase keywords where appropriate.	25 years ago
Tom Lane	b57705673d	txtidx datatype for full text indexing with GiST. ... From Oleg Bartunov and Teodor Sigaev.	25 years ago
Bruce Momjian	c24216bea8	Fix reverse FOR loop to work properly, uppercase cleanup in file.	25 years ago
Bruce Momjian	ec614c9872	Remove locale/multibyte in HISTORY file, for Tatsuo.	25 years ago
Bruce Momjian	c0b2bbf42e	Add WAL mmap() mention.	25 years ago
Bruce Momjian	68966634b2	Update TODO list.	25 years ago
Bruce Momjian	6790f21441	Update TODO list.	25 years ago
Bruce Momjian	63a22cd2dd	Update TODO list.	25 years ago
Bruce Momjian	129b19f685	Update TODO list.	25 years ago
Bruce Momjian	d8f88f01f0	Update TODO list.	25 years ago
Bruce Momjian	010e8144cd	Update TODO list.	25 years ago
Bruce Momjian	7d9d026323	Update TODO list.	25 years ago
Bruce Momjian	7bce3e95cf	Remove mutex mention. Fixed now.	25 years ago
Bruce Momjian	182722f737	Update TODO list.	25 years ago
Hiroshi Inoue	0420342af1	Update the version of psqlodbc driver.	25 years ago
Bruce Momjian	ffcad12769	Update TODO list.	25 years ago
Tatsuo Ishii	f426465ba9	Add a new function "pg_client_encoding" which returns the current client ... side encoding name. This is necessary for client API's such as JDBC to perform correct encoding conversions. See my email "[HACKERS] pg_client_encoding" 10 Sep 2001.	25 years ago
Hiroshi Inoue	9d13fcf0af	Fix the bug reported by Chris Lee.	25 years ago
Tom Lane	f9e6e27c87	Break transformCreateStmt() into multiple routines and make ... transformAlterStmt() use these routines, instead of having lots of duplicate (not to mention should-have-been-duplicate) code. Adding a column with a CHECK constraint actually works now, and the tests to reject unsupported DEFAULT and NOT NULL clauses actually fire now. ALTER TABLE ADD PRIMARY KEY works, modulo having to have created the column(s) NOT NULL already.	25 years ago
Bruce Momjian	e98476eb03	Document use of GEQO param in subquery pullups.	25 years ago
Bruce Momjian	9e642cd7ef	Update TODO list.	25 years ago
Bruce Momjian	c19ff887c6	Add documention for ecpg -209 error.	25 years ago
Tom Lane	97d0c8b219	Suppress gcc warnings.	25 years ago
Bruce Momjian	78f7ba13cb	Tatsuo Ishii <t-ishii@sra.co.jp> writes: ... > As you can see, psql reconnect as any user if the password is same as > foo. Of course this is due to the careless password setting, but I > think it's better to prompt ANY TIME the user tries to switch to > another user. Comments? Yeah, I agree. Looks like a simple change in dbconnect(): /* * Use old password if no new one given (if you didn't have an old * one, fine) */ if (!pwparam && oldconn) pwparam = PQpass(oldconn); to /* * Use old password (if any) if no new one given and we are * reconnecting as same user */ if (!pwparam && oldconn && PQuser(oldconn) && userparam && strcmp(PQuser(oldconn), userparam) == 0) pwparam = PQpass(oldconn); regards, tom lane	25 years ago