Re: [pgadmin-support] [SQL] Change a field to sequence (serial)

2007-02-25 Thread Rodrigo De León

On 2/24/07, Ezequias Rodrigues da Rocha <[EMAIL PROTECTED]> wrote:

Hi lists,

Is there possible to change a bigint field (primary key) to a serial ?
If yes how it is possible ?

I was trying to do that but the pgadmin don't enable the change to sequence.

What is the problem my friends ?

Regards
Ezequias
http://ezequiasrocha.blogspot.com/


See:
http://www.postgresql.org/docs/8.2/static/datatype-numeric.html#DATATYPE-SERIAL
http://www.postgresql.org/docs/8.2/static/functions-sequence.html

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [pgadmin-support] Crashing v1.6.2 with a syntax error

2007-02-25 Thread Erwin Brandstetter

Hi Dave!

[EMAIL PROTECTED] wrote:

Erwin Brandstetter wrote:
  
(...)

The "essential" part ist the "%" at the end of the first string.



Yeah, in some cases that string was going through a printf variant, so
it was trying to expand the %. Fixed for 1.6.3.

  

After that the error message was scrambled differently:
   loc = '%a' loc = ''



Yeah, it would have been unpredictable because of the bug above. Can you
test the SVN code please, and let me know if there's still a problem.

Cheers, Dave.


Testing pgAdmin III v1.6.3 rev: 5941M on Win XP (SP2), hosts are PG 8.1.8 on 
Debian Sarge and PG 8.2.1 on Debian Etch.

The new Windows binary I have got from Dave does not crash any more. The 
problem at had seems fixed. :)


I noticed, however, that another issue mentioned in my report is still 
there. Referring to what Laurent ROCHE posted initially on Tue, 9 Jan 
2007: "Still no text for error messages only numbers for 1.6.2 (aka the 
Saga continues)". I will post a reply to that thread.



Regards
Erwin

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re : [pgadmin-support] pgadmin as main postgresql GUI interface

2007-02-25 Thread Laurent ROCHE
Hi,

my two cents on that interesting thread:
I come from a database developer background.
I have used quite a few tools in the past years on different RDBMs (mainly 
Sybase, MS SQL-Server, and a bit of Oracle).

When I have started using PG at the end of last year, I looked at the tools 
around.
I am quite pleased with PG Admin but I was also looking at other tools of 
easier access for non developer users.

I did not find any thing really satisfying but using OOo connecting with JDBC, 
did the job OK : it is possible to browse through the tables, to create queries 
graphically and to modify tables.
I even used it at the beginning to create queries graphically (when I did not 
the DB well). Today, I do not use it anymore, but some in our team do, and that 
works OK for not too demanding users.
Also you might want to have a look at DB-Visualizer: it's more a developper 
tool but it could work for you too.

Last point (but not least ;-) ! ), we are only using OOo on Windows XP, so I 
don't know about the reliability on AMD with Debian, but the functions should 
be the same.
May be the JDBC connection will solve some of your troubles.

 
Have fun,
[EMAIL PROTECTED]
The Computing Froggy

- Message d'origine 
De : Seb <[EMAIL PROTECTED]>
À : pgadmin-support@postgresql.org
Envoyé le : Dimanche, 25 Février 2007, 6h05mn 45s
Objet : Re: [pgadmin-support] pgadmin as main postgresql GUI interface

On Sat, 24 Feb 2007 19:54:13 +0100,
Michael Eschweiler <[EMAIL PROTECTED]> wrote:

[...]

> You could try knoda (www.knoda.org) and/or rekall
> (www.rekallrevealed.org).  Unless you don't want do more complicated
> things knoda could be a good choice (but I don't know nothing about the
> report generator - I never used it). As of my experience knoda seems to
> be a little buggy: For example if you try to trigger some code in python
> from a combobox the program executes it twice.  But for simple purposes
> it should work.  I tried rekall in a very early stage (2 or 3 years ago)
> but as the layout of texts in the different widgets on the screen wasn't
> that good, and as I wanted to work with larger texts I changed to
> knoda. Now rekall seems to have improved considerably and comes with a
> detailed manual.

Thanks, I should check the current state of knoda.  Last time I tried it
~1 yr ago, it allowed only minimal functionality to interact with
PostgreSQL.  Kexi invariably crashes in my system (AMD64) when doing
things with PostgreSQL.  I tried rekall during the last few days, but it
crashes soon after connecting to a database.  Some of these problems may
be happening only in AMD64.  Indeed, Debian's Openoffice.org packages are
very recent, but are already more stable than the apps mentioned above.
However, it also crashes frequently during connections with PostgreSQL (or
MySQL) connections and, again, functionality is very limited.
Particularly, I'd like to have some GUI do something like M$ Access'
relationship.

In the meantime, I've also tried to figure out how to use my old *.mdb
files through ODBC directly.  Basically, using unixODBC to connect to the
*.mdb from a *nix app (say GNU R for stats analysis).  I've been using
Codeweavers' Crossover as I migrate things over to PostgreSQL, and this
plan seems possible:

http://www.codeweavers.com/support/docs/wine-user/config-odbc

although I haven't yet understood the last step of their configuration
guidelines.


-- 
Seb


---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate









___ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur 
Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


Display of error message (was: Re: Re : [pgadmin-support] Crashing v1.6.2 with a syntax error)

2007-02-25 Thread Erwin Brandstetter

Hi developers! Hi Laurent!

[EMAIL PROTECTED] wrote:

Hello Erwin,

I am interested in the part "I get an error message with only the error code".

I have the same problem, however in the rest of your message you do have an error message with the error code 
" FEHLER: Fehler »Syntaxfehler« bei »loc«

SQL state: 42601
Character: 1"

How do you achieve this ?

My problem is that, if my database is in UTF-8, I will not get any error 
messages, just the code.
Is that the same for you ? Have you found a solution to have an error message ?
So far we have not been able to reproduce this error: it seems its due to my PG 
server configuration (Ubuntu with French locale), other configurations 
(including on WinXP machine) work fine.

- Message d'origine 
De : Erwin Brandstetter <[EMAIL PROTECTED]>
À : pgadmin-support@postgresql.org
Envoyé le : Mercredi, 21 Février 2007, 2h06mn 21s
Objet : [pgadmin-support] Crashing v1.6.2 with a syntax error

(...)

 Look at the following query:
 select * from loc where loc like 'a%' loc = 'b';
Note the syntax error: "and" is missing in the WHERE clause. If I run 
this from the SQL query dialogue window I get an error message with only 
the error code - but that has been reported before.


FEHLER: Fehler »Syntaxfehler« bei »loc«
SQL state: 42601
Character: 1


Laurent, I was not aware that you were the one to report the problem 
with missing error messages in the first place.
In the new Windows version Dave has compiled from SVN I still get a 
number instead of additional additional information:
(Using the faulty query from above:  select * from loc where loc like 
'a%' loc = 'b'; )


   FEHLER: Fehler »Syntaxfehler« bei »loc«
   SQL state: 42601
   Character: 39

Laurent, is that what you see, too?
Actually, the error message IS shown in my case. Only, I get a number 
instead of an additional line of explanation which psql would display.

That would not be by design, would it?

pgAdmin v1.4.3 only gave ponly 1 line:
   FEHLER:  Fehler »Syntaxfehler« bei »loc« at character 39

psql (v8.1.8):
   event=# select * from loc where loc like 'a%' loc = 'b';
   FEHLER:  Fehler »Syntaxfehler« bei »loc« at character 39
   ZEILE 1: select * from loc where loc like 'a%' loc = 'b';
  ^
psql (v8.2.1):
   event=# select * from loc where loc like 'a%' loc = 'b';
   FEHLER:  Fehler »Syntaxfehler« bei »loc«
   LINE 1: select * from loc where loc like 'a%' loc = 'b';
 ^
(On a sidenote: I am surprised psql gives English "LINE 1:" instead of 
"German "ZEILE 1:", as lc_messages = 'de_AT.UTF-8')


Changing the user language in the pgadmin options to German or English 
has no effect on the issue (except for changing the language, of course).




Some of my setup data (if needed):

Server 1, PG 8.1.8 on Debian Sarge:
===

select version();
   PostgreSQL 8.1.8 on i386-pc-linux-gnu, compiled by GCC cc (GCC) 
3.3.5 (Debian 1:3.3.5-13)


show client_encoding;
   UNICODE

SELECT pg_catalog.pg_encoding_to_char(d.encoding)
FROM pg_catalog.pg_database d JOIN pg_catalog.pg_roles r ON d.datdba = r.oid
WHERE d.datname = 'event';
   UTF8

From my postgresql.conf:
   datestyle = 'ISO,European'
   lc_messages = '[EMAIL PROTECTED]'
   lc_monetary = '[EMAIL PROTECTED]'
   lc_numeric = '[EMAIL PROTECTED]'
   lc_time = '[EMAIL PROTECTED]'

From the server OS (should be irrelevant!)
   [EMAIL PROTECTED]:~$ locale
   [EMAIL PROTECTED]
   {all LC_* variables}="[EMAIL PROTECTED]"



Server 2, PG 8.2.3 on Debian Etch:
==

select version();
   PostgreSQL 8.2.3 on i486-pc-linux-gnu, compiled by GCC cc (GCC) 
4.1.2 20061115 (prerelease) (Debian 4.1.1-21)


show client_encoding;
   UNICODE

SELECT pg_catalog.pg_encoding_to_char(d.encoding)
FROM pg_catalog.pg_database d JOIN pg_catalog.pg_roles r ON d.datdba = r.oid
WHERE d.datname = 'event';
   UTF8

From my postgresql.conf:
   datestyle = 'iso, ymd'
   lc_messages = 'de_AT.UTF-8'
   lc_monetary = 'de_AT.UTF-8'
   lc_numeric = 'de_AT.UTF-8'
   lc_time = 'de_AT.UTF-8'

From the server OS (should be irrelevant!)
   [EMAIL PROTECTED]:~$ locale
   LANG=de_AT.UTF-8
   {all LC_* variables}="de_AT.UTF-8"


Client: pgAdmin III v1.6.3 rev: 5941M on Win XP (SP2)



I will happily provide more data if needed.


Regards
Erwin

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [pgadmin-support] pgadmin as main postgresql GUI interface

2007-02-25 Thread Guillaume Lelarge

Seb a écrit :

Hi,

I'm exploring ways to interact with postgresql through a GUI.  I'm in a
Debian testing system (AMD64) and have found very few options.  I really
like pgadmin for the administrative tasks with postgresql, but I'm looking
for something for day to day data entry, querying, and report generation.
I come from an M$ Access background, where I was used to clicking around
for these tasks.  Openoffice.org does seem to have similar functionality,
but I haven't been able to set it up to work with postgresql.  I would
appreciate some suggestions from other postgresql/pgadmin users.  Thanks.




You can also try glom. It's a gnome app that does only this : list table 
contents, view details, create simple report. I went to a glom 
conference at FOSDEM. It seems pretty interesting.


Regards.


--
Guillaume.


---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at

   http://www.postgresql.org/about/donate