I've not had time to translate everything yet, but here is what i've got
now. I would like it to be commited.
Two of the files are complete, the last strings I hope I will have time to
complete before the release, but who knows. I'm in a busy period wrt my
work so I don't know if I will make it.
On Thu, 9 Oct 2003, Bruce Momjian wrote:
> Uh, I can't apply this to 7.4 unless you can get others to agree it
> should be added. Sorry.
It looks like the patch changes translated strings which isn't supposed to
happen. It can of course still be accepted, that's not my call.
ps. Unified diffs (
On Sat, 18 Oct 2003, Dennis Bjorklund wrote:
> All strings in the swedish psql.po have been translated.
The above have not been commited.
I also see on the translate page that pg_dump is now at 99%, it was at a
beautiful 100% before..
Is it possible to get cvs access, with say a promise t
On Sun, 14 Dec 2003, Bruce Momjian wrote:
> change to the code. We already have a GUC write of non-default values
> for exec and no one had issues with that. Of course, this one is
> per-backend.
>
> Yea, we could use shared memory for this too, but I don't see a problem
> with using the file s
On Sun, 14 Dec 2003, Bruce Momjian wrote:
> > Why not use an anonymous pipe to send data from the parent to the child
> > process?
>
> Doesn't that require the postmaster to stay around to feed that
> information into the pipe or can the postmaster just shove the data and
> continue on, and how d
On Mon, 15 Dec 2003, Claudio Natoli wrote:
> Moreover, in general, how do we handle things like this? IMHO, I'd rather
> live with a few kludges (that don't impact the *nix code) until the Windows
> port is actually a reality
As long as it does not hurt the unix code it's not a big problem as I s
I've found a string not marked for translation.
--
/Dennis Björklund
Index: src/bin/psql/describe.c
===
RCS file: /cvsroot/pgsql-server/src/bin/psql/describe.c,v
retrieving revision 1.91
diff -u -c -r1.91 describe.c
*** src/bin/psql/
On Wed, 21 Jan 2004, Peter Eisentraut wrote:
> Am Mittwoch, 21. Januar 2004 02:16 schrieb Bill Moran:
> > BTW: Why is this frowned apon so? Are there compilers that have
> > problems with it?
>
> Yes. Search the archives for "AIX". :-)
I googled a little for the aix compiler and it looks like
This small patch updates the information schema to show function parameter
names when they exist.
--
/Dennis Björklund
Index: doc/src/sgml/information_schema.sgml
===
RCS file: /cvsroot/pgsql-server/doc/src/sgml/information_schema.sg
I've been testing pg using valgrind and have found a read of an
uninitialized buffer. In the hba-tokenizer when we have not read any
characters (or too few) we still perform a couple of:
strncmp(start_buf,"sameuser",8)
Since this is done on random data it might return true although we have
not
On Sun, 1 Feb 2004, Andrew Dunstan wrote:
> As for the test being outside the "if" statement, it is true that that
> might waste a few cycles, but it hardly matters.
The cycles are not important. My "fix" wasn't the most optimized either if
one should count cycles. It was terminating the string t
On Thu, 26 Feb 2004, Neil Conway wrote:
> The improved text is still wrong: initcap() no longer uses whitespace
> to separate words.
Aha, I didn't know the function had changed at all.
How does it work with respect to the locale? When you say that a word is a
sequence of alphanum characters, wh
The doc for the trim functions does not say that the second argument can
be omitted. This patch fixes it. It also fixes that the type text was not
wrapped as text.
I can not build the docs myself, but i'm pretty sure it's correct.
Is it okay to commit this? Should I do it on the 7.4 branch also
On Wed, 10 Mar 2004, Tom Lane wrote:
> > nconway=# select 'Infinity'::float8;
> > ERROR: type "double precision" value out of range: overflow
>
> This works in 7.4 and older releases. Sounds to me like you broke it.
It does not work on 7.3 and 7.4 when I try.
Looking at the currect cvs code i
On Thu, 11 Mar 2004, Shachar Shemesh wrote:
> >It's a bit strange that this int is unsigned and the others are signed.
> >
> Not that strange if you consider the fact that making it signed will not
> leave much room for actually using it.
>
> In any case, that's just the way it is:
> http://ms
Here is a small doc patch that says that initcap lowercases the rest of
the characters in the string. The current doc suggests that it only
touches the first character in each word, which is not what the function
does.
Maybe we should change the example to be 'hi THOMAS' instead of 'hi
thomas'.
It's not much text, but someone who speaks english might want to look at
it.
If it's okay I can commit.
--
/Dennis Björklund
Index: doc/src/sgml/ref/create_function.sgml
===
RCS file: /cvsroot/pgsql-server/doc/src/sgml/ref/create_f
On Thu, 24 Jun 2004, Tom Lane wrote:
> 1. We usually leave spaces around brackets in syntax definitions, so
> I'd go for "... [ argname ] ..." not "... [argname] ..."
I saw both in that very rule (later there is an [EXTERNAL]) so I guessed
that one use what looks best at different places. But co
Here is a trivial fix for some error messages that was not translated
before. I've also gotten rid of some cut and paste of strings. That
doesn't always work (like in this case) when translating.
--
/Dennis Björklund
---(end of broadcast)---
TIP
On Sun, 27 Jun 2004, Dennis Bjorklund wrote:
> Here is a trivial fix for some error messages that was not translated
> before. I've also gotten rid of some cut and paste of strings. That
> doesn't always work (like in this case) when translating.
And here is the patch al
There is no way to show schema permissions in psql.
The alternatives are:
1) A new \dpn command
2) Extend \dp to also show rights for schemas, but then we need
an extra column to describe what kind of object it is, and it
would mess up the pattern stuff.
3) Do nothing and let pe
On Wed, 30 Jun 2004, Kris Jurka wrote:
> > There is no way to show schema permissions in psql.
> >
> > 4) Since \dn only shows the name and the owner we can simply
> > add a permission column.
>
> Someone requested that \dn+ also show the comment for the schema, if
> you're messing aroun
On Fri, 2 Jul 2004, Peter Eisentraut wrote:
> You could extend \z (don't know where that name came from) so that \zX show
> the permissions for things that \dX displays.
Yes, that was number 1) on the list
1) A new \dpn command
\dp and \z is the same thing. Any solution works for me. The ma
The doc doesn't state in what range the argument to setseed() should be.
Some tests suggest that only values in the range -1.0 to 1.0 work as a
seed and values outside of that give the same sequence of random numbers.
I've attached a trivial one line patch (this is the patch list after
all),
Tom Lane skrev:
setseed(dp)
int
- set seed for subsequent random() calls
+ set seed for subsequent random() calls (value
between -1.0 and 1.0)
Looking at the code, it would appear that the intended range is 0 to 1.
Ok.
What about the return value? The doc didn'
Tom Lane skrev:
You could imagine trying to do
% a byte at a time (and indeed that's what I'd been thinking it did)
but that gets you out of sync which breaks the _ case.
It is only when you have a pattern like '%_' when this is a problem and
we could detect this and do byte by byte when it's
version of
--- 1121,1127
! Add a function lastval() (Dennis Björklund)
lastval() is a simplified version of
***
*** 4236,4242
! Allow function parameters to be declared with names (Dennis
On Sat, 7 Aug 2004, Tom Lane wrote:
> shy of a load --- for instance I see that pg_utf_mblen thinks there are
> no UTF8 codes longer than 3 bytes whereas your code goes to 4. I'm not
> an expert on this stuff, so I don't know what the UTF8 spec actually
> says. But I do think you are fixing the
On Sat, 7 Aug 2004, Tom Lane wrote:
> question at hand is whether we can support 32-bit characters or not ---
> and if not, what's the next bug to fix?
True, and that's hard to just give an answer to. One could do some simple
testing, make sure regexps work and then treat anything else that migh
On Sat, 7 Aug 2004, John Hansen wrote:
> should not allow them to be stored, since there might me someone using
> the high ranges for a private character set, which could very well be
> included in the specification some day.
There are areas reserved for private character sets.
--
/Dennis Björk
On Sat, 7 Aug 2004, Tatsuo Ishii wrote:
> More seriously, Unicode is filled with tons of confusion and
> inconsistency IMO. Remember that once Unicode adovocates said that the
> merit of Unicode was it only requires 16-bit width. Now they say they
> need surrogate pairs and 32-bit width chars...
>
Today "pg_controldata --help" gives this usage info:
| Usage:
| pg_controldata [OPTION]
|
| Options:
| DATADIRshow cluster control information for DATADIR
| --help show this help, then exit
| --version output version information, then exit
|
| If no data directory is
Here is a small patch that implements a function lastval() that
works just like currval() except that it give the current
value of the last sequence used by nextval().
Using this function one can do:
# CREATE TABLE abc (a serial, b int);
CREATE TABLE
# SELECT lastval();
ERROR: nextval have not
On Sun, 8 May 2005, Tom Lane wrote:
> Why is that a good idea? In a complex application it'd be awfully easy
> to break logic that depends on such a thing.
Of course it can break. currval() can also break in a complex application
with triggers and rules that do things the developer does not expe
On Sun, 8 May 2005, Tom Lane wrote:
> Like, say, the sequence being deleted before the lastval call?
Then you get an error message. Same thing if you have revoked the rights
on the sequence before you call lastval().
In this case you can get a value that belong to a sequence that is
deleted. Is
On Thu, 2 Jun 2005, Neil Conway wrote:
> > Here is a small patch that implements a function lastval() that
>
> Have you had a chance to respin this patch per my earlier comments on
> the implementation, Dennis?
I've been spending my free time on another project and I don't multitask
very well :
On Thu, 19 May 2005, Neil Conway wrote:
> > +errmsg("currval of sequence with OID %d is not
> > yet defined in this session",
> > + last_used_seq->relid)));
>
> See above; however, when will this error actually be invoked? (Th
On Mon, 6 Jun 2005, Tom Lane wrote:
> You could fix that by remembering exactly which sequence produced
> the lastval and checking its permissions ...
That is what the implementation does. Instead of remembering the last
value it rememebers the last sequence (and it contains the last value for
38 matches
Mail list logo
