Re: [BUGS] order by question.

2007-05-04 Thread Ennio-Sr
* Jose Blanco <[EMAIL PROTECTED]> [040507, 14:28]:
> This second time I did, see
> 
> select author, sort_author from itemsbyauthor where sort_author like 'tan%'
> order by 2;
> 
> 
> "order by 2"
> 
> Or am I not understanding something?

Hi Jose,
have you tried to modify your query as others suggested? i.e.:

--> select author, sort_author from itemsbyauthor where sort_author like
'tan% ORDER BY sort_author;
  
HTH
Regards,
Ennio.

-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo.   \\?//
 Fa' qualche cosa di cui non sei capace!"  (diceva Henry Miller) ](°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that.  )=(
 Do something you aren't good at!" (as Henry Miller used to say) ]

---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org


Re: [BUGS] order by question.

2007-05-04 Thread Ennio-Sr
* Ennio-Sr <[EMAIL PROTECTED]> [040507, 23:52]:
> * Jose Blanco <[EMAIL PROTECTED]> [040507, 14:28]:
> > This second time I did, see
> > 
> > select author, sort_author from itemsbyauthor where sort_author like 'tan%'
> > order by 2;
> > 
> Hi Jose,
> have you tried to modify your query as others suggested? i.e.:
> 
> --> select author, sort_author from itemsbyauthor where sort_author like
> 'tan%' ORDER BY sort_author;
>

Oops ... I missed your "order by 2" ... Sorry ;(

-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo.   \\?//
 Fa' qualche cosa di cui non sei capace!"  (diceva Henry Miller) ](°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that.  )=(
 Do something you aren't good at!" (as Henry Miller used to say) ]

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


[BUGS] Psql 'Expanded display (\x)' behaviour

2003-04-04 Thread Ennio-Sr
Hello!
I'm new to this list and hope it is the right one (I posted to
General and Novice but got no answer).

I know that issues concerning the (erroneously) so called extended ASCII
chars are of partial interest to English speaking people ... so I should
be very grateful if any of you could confirm that:
toggling on/off the 'Expanded display' (in psql) does affect the display
of non-ascii chars.

Regards,
Ennio.

---
PS: I'm using:
Linux .. 2.2.19pre17 #1 Tue Mar 13 22:37:59 EST 2001 i586 unknown
PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.95.4
$ /usr/lib/postgresql/bin/pg_controldata /var/lib/postgres/data
[cut]
LC_COLLATE:   it_IT
LC_CTYPE: it_IT

but tried other charsets with the same result: accented letters display
ok only when 'expanded display' is turned off (in which case, however,
the pager doesn't work!).


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html


Re: [BUGS] Psql 'Expanded display (\x)' behaviour

2003-04-05 Thread Ennio-Sr
> Ennio-Sr writes:
> 
> > toggling on/off the 'Expanded display' (in psql) does affect the display
> > of non-ascii chars.
> 
> Not at all.  It's only an alternative table format.

Yes, but when I try to display this 'alternative table format' I found
that some of the chars (precisely those not in ascii 0-127) loose the
appearance ('glyph') they have when expanded display is off!

OK, I'll try to better explain what I mean:
I enter my db with $ psql mydb, then _I create a test table:_

mydb=#create table pro_chars (code text, glyph text);

and _insert some values:_

mydb=#insert into pro_chars values ('ALT+176', '°');
mydb=#insert into pro_chars values ('ALT+177', '±');
mydb=#insert into pro_chars values ('ALT+178', '²');
mydb=#insert into pro_chars values ('ALT+171', '«');
mydb=#insert into pro_chars values ('ALT+187', '»');
mydb=#insert into pro_chars values ('ALT+233', 'é');
mydb=#insert into pro_chars values ('A with grave', 'à');

(I typed the code values as you read them and the glyphs (which won't
display on your screen if you aren't in Latin1, perhaps) pressing in
turn: apostrophe, LeftAltKey + numbers on numerical keypad, apostrophe.)

Finally I _display my table:_

mydb=#select * from pro_chars;

and _everything is ok_, i.e. correct glyphs corresponding to the codes
are displayed.

Then I _toggle on the expanded display:_

mydb=#\x 

and again:

mydb=#select * from pro_chars;

but (in the glyph column) I get, respectively: 0, 1, 2, +, ;,  , 1

Could you please reproduce this on your PC and see what happens?

> Perhaps the problem is that the pager does not handle the accented
> characters right.

Ehm ... I don't think pager has anything to do with the chars; I quoted
it only to underline the necessity for me to use 'Expanded display on'
as the only mean to see one page at a time, since I verified that pager
is not working with my tables!
It doesn't even work with the display of history: if I do:
mydb=# \s
the whole history will scroll on my screen and I'll be able to see last
page only! I read somewhere (/usr/share/doc/postgres-doc?) that pager
is not very reliable as to the correct judgement on where to stop!

Thanks for your attention, Peter.
Regards,
Ennio.
-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. \\?//
 Fa' qualche cosa di cui non sei capace!"   (diceva Henry Miller) ] (°|°)
[Why to use Win$ozz (I say) if ... "even a fool can do that. )=(
 Do something you aren't good at!" (used to say Henry Miller) ]


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html


Re: [BUGS] pg_dump silently fails

2005-06-14 Thread Ennio-Sr
* Bruce Momjian  [140605, 14:00]:
> Tom Lane wrote:
> > Brandon Keepers <[EMAIL PROTECTED]> writes:
> > > I've been wresting with this problem since 8.0.1 and am able to
> > > duplicate it on 6 different installations.  If I compile postgres from
> > > source, everything works fine.  If I install the RHEL 4 ES RPM, pg_dump
> > > silently fails.
> > 
> > Is SELinux in enforcement mode, and if so does turning it off change
> > things?
> 
> Should we check for a buggy SELinux and report a meaningful error
> message on failure?
> 

Sorry to interfere ;)
You might be interested to know that there was a complaint about SELinux
blocking OpenOffice too. See ML 'users@openoffice.org' June 13 'Previously
working OOo ...'
Regards,
Ennio.
-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo.   \\?//
 Fa' qualche cosa di cui non sei capace!"  (diceva Henry Miller) ](°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that.  )=(
 Do something you aren't good at!" (as Henry Miller used to say) ]

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]