This is the sort of question that is far better suited to the
pgsql-gene...@postgresql.org mailing list or the
pgadmin-supp...@postgresql.org mailing list, but the answer is that
you should use the copy sql command:
http://www.postgresql.org/docs/current/static/sql-copy.html
--
Regards,
Peter Ge
Hi,
I'm using pgadmin to administrate my postgreSQL database.
But now I was told to import a text file containing a table with fields
seperated by ';'
How Do I do that?
Regards
Hi all,
On Thu, 2010-04-08 at 07:45 -0400, Robert Haas wrote:
> >> 2010/4/8 Thom Brown :
> >> > So you could write:
> >> >
> >> > DELETE FROM massive_table WHERE id < 4000 LIMIT 1;
> I've certainly worked around the lack of this syntax more than once.
> And I bet it's not even that hard t
On Thu, Apr 8, 2010 at 7:05 AM, Thom Brown wrote:
> On 8 April 2010 11:55, Ian Barwick wrote:
>>
>> 2010/4/8 Thom Brown :
>> > I couldn't find any discussion on this, but the request is quite
>> > straightforward. Implement a LIMIT on DELETE statements like SELECT
>> > statements.
>> >
>> > So y
On 8 April 2010 11:55, Ian Barwick wrote:
> 2010/4/8 Thom Brown :
> > I couldn't find any discussion on this, but the request is quite
> > straightforward. Implement a LIMIT on DELETE statements like SELECT
> > statements.
> >
> > So you could write:
> >
> > DELETE FROM massive_table WHERE id <
ja...@gmail.com>>
Date: Tue, Dec 15, 2009 at 10:03
Subject: Re: [HACKERS] pgAdmin III: timestamp displayed in what time zone?
To: Andrew Dunstan mailto:and...@dunslane.net>>
Thanks for being so polite. At least Greg Smith suggested the right
list to ask. I see that some people still
Looks like Andrew Dunstan didn't want to go public...
Fred
-- Forwarded message --
From: Fred Janon
Date: Tue, Dec 15, 2009 at 10:03
Subject: Re: [HACKERS] pgAdmin III: timestamp displayed in what time zone?
To: Andrew Dunstan
Thanks for being so polite. At least Greg
Le mardi 15 décembre 2009 à 06:30:15, Greg Smith a écrit :
> [...]
> > BTW, this list is listed as the list for tech questions in the pgAdmin
> > tips, therefore if you don't want to be disturb, you might want to
> > remove it from the pgAdmin tips.
>
> When I look at http://www.pgadmin.org/suppor
On Tue, Dec 15, 2009 at 5:30 AM, Greg Smith wrote:
> When I look at http://www.pgadmin.org/support/ for example it suggests the
> right list. I only see this one listed in the Translation section, as the
> place to ask to get added to the translators list. Does anyone know where
> the tips sect
Fred Janon wrote:
Thanks Greg, at least among the socially unacceptable insults I got
the the right list to post my question in.
Aww, is somebody having a case of the Monday's?
Frankly that was all useful advice. I was pointing out that despite
what you thought, you might actually be decreas
On Mon, Dec 14, 2009 at 9:08 PM, Fred Janon wrote:
> Thanks Greg, at least among the socially unacceptable insults I got the the
> right list to post my question in. I am trying to get some help from
> (supposedly) helping and knowledgeable people and I get insults in return.
I don't want to make
Thanks Greg, at least among the socially unacceptable insults I got the the
right list to post my question in. I am trying to get some help from
(supposedly) helping and knowledgeable people and I get insults in return.
BTW, this list is listed as the list for tech questions in the pgAdmin tips,
t
Fred Janon wrote:
Sorry if if's a double post, but I thought that it would be more
likely I would get an answer on the hackers list.
In that case just posting here would have been better than hitting
both. I usually ignore any request for help that is posted on more than
one list just to draw
Sorry if if's a double post, but I thought that it would be more likely I
would get an answer on the hackers list.
Thanks
Fred
-- --
From: Fred Janon
Date: Mon, Dec 14, 2009 at 19:04
Subject: pgAdmin III: timestamp displayed in what time zone?
To: pgsql-gene...@postgresql.org
On Tue, Sep 30, 2008 at 2:19 AM, Robins Tharakan <[EMAIL PROTECTED]> wrote:
> Hi,
> While making a complex database back-end, I have at-hand about 200 odd
> functions and frankly 'management of functions' is already getting quite
> tedious. Since the count is certain to rise, I am looking for a goo
Roberto Icardi wrote:
Also, please set pgAdmin to 'Debug' log level (under File->Options),
create a new log of you recreating the crash (using direct debugging,
not a global breakpoint) and then send me the logfile.
Done
Doesn't shed any light though unfortunately. Do you have a firewall on
I've tried on the win2000 virtual machine (running on virtualpc 2007)...
same error!
So, or I make something wrong (but I really don't understand what), or is
that particular pc,
or maybe uninstalling 8.2 left something dirty for 8.3. I need a clean vm
for testing
third option, but requires some
Also, please set pgAdmin to 'Debug' log level (under File->Options),
create a new log of you recreating the crash (using direct debugging,
not a global breakpoint) and then send me the logfile.
Done
Doesn't shed any light though unfortunately. Do you have a firewall on
that box? If so, can yo
Roberto Icardi wrote:
>> When you attempt to debug it, do you see the parameter dialogue before
>> it crashes, or does it go immediately?
>>
>
> if I try debug->debug it goes immediately
> if I try debug->set breakpoint I can see debugger window but is
> completely empty and inactive
>
>
>
>> A
- Original Message -
From: "Roberto Icardi" <[EMAIL PROTECTED]>
To: "Dave Page" <[EMAIL PROTECTED]>
Sent: Monday, October 22, 2007 5:31 PM
Subject: Re: [HACKERS] pgadmin debug on windows
When you attempt to debug it, do you see the parameter dialogue
Roberto Icardi wrote:
> CREATE OR REPLACE FUNCTION public.prova(provain character varying)
> RETURNS character varying AS
> $BODY$
> begin
> if (provain = 'A') then
>return 'INVALIDO';
> else
>return 'VALIDO';
> end if;
> end;
> $BODY$
> LANGUAGE 'plpgsql' VOLATILE
> COST 100;
> ALTER
Please post the definition of an affected function, along with the
output from the following queries:
select * from pldbg_get_proxy_info();
select * from pldbg_get_target_info('16480', 'o');
(where 16480 is replaced with the oid of the affected function).
Thanks, Dave
CREATE OR REPLACE FUN
Roberto Icardi wrote:
> Yes, they are all there
> I've also tried on a newly created database instead of testing on a
> restored from 8.2. backup but with
> the same behaviour :-(
Please post the definition of an affected function, along with the
output from the following queries:
select * fr
ED]>
Cc:
Sent: Monday, October 22, 2007 4:09 PM
Subject: Re: [HACKERS] pgadmin debug on windows
Roberto Icardi wrote:
Dave,
the problem isn't with a particular function. Debug does not work with
every function I try, even with the simplest one, always with the same
behaviour I'v
Roberto Icardi wrote:
> Dave,
>
> the problem isn't with a particular function. Debug does not work with
> every function I try, even with the simplest one, always with the same
> behaviour I've previously explained.
> I repeat, my postgresql server is an 8.3 beta 1 installed on the same
> machin
Dave,
the problem isn't with a particular function. Debug does not work with every
function I try, even with the simplest one, always with the same behaviour I've
previously explained.
I repeat, my postgresql server is an 8.3 beta 1 installed on the same machine
where pgadmin III 1.8 is insta
Roberto Icardi wrote:
> Hello,
>
> I've installed on a windows xp machine beta 1 of postgresql 8.3 and
> pgadmin III 1.8.
> I've loaded a backup of a database from a 8.2.5 machine, for testing
> purpose, and tried
> the new functionality of plpgsql debug of functions.
>
> But I was disappointed
Hello,
I've installed on a windows xp machine beta 1 of postgresql 8.3 and pgadmin III
1.8.
I've loaded a backup of a database from a 8.2.5 machine, for testing purpose,
and tried
the new functionality of plpgsql debug of functions.
But I was disappointed to see that does not work.
I try to deb
Artur Wasilewski wrote:
Hi,
I was wondering if there is any possibility to add an enhancement in
pgAdmin Query.
Now, when we do "select * from smth", results are listed in DataOutput
tab and there we have columns with the same width (something about
260px currently). It is realy annoying that in
Hi,
I was wondering if there is any possibility to add an enhancement in
pgAdmin Query.
Now, when we do "select * from smth", results are listed in DataOutput
tab and there we have columns with the same width (something about
260px currently). It is realy annoying that in most cases user don't
see
ops, error when typing the name of the list. excuses
2007/4/21, Euler Taveira de Oliveira <[EMAIL PROTECTED]>:
Nabucodonosor Coutinho wrote:
> I translated some things and I corrected many others in the
> translation of pgadmin3 for Portuguese of Brazil. It incorrectly had
> much translated thi
Nabucodonosor Coutinho wrote:
> I translated some things and I corrected many others in the
> translation of pgadmin3 for Portuguese of Brazil. It incorrectly had
> much translated thing, and much thing with translation of one another
> one. It would like to know you as I can disponibilizar this m
Hello,
I translated some things and I corrected many others in the
translation of pgadmin3 for Portuguese of Brazil. It incorrectly had
much translated thing, and much thing with translation of one another
one. It would like to know you as I can disponibilizar this my small
contribution.
--
Nabu
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
???Sent: 06 April 2006 10:24To:
pgsql-hackers@postgresql.orgSubject: [HACKERS] pgadmin III's
Chinese simplified translations
i have continued the pgadmin III's Chinese simplified
transla
i have continued the pgadmin III's Chinese simplified
translations,hope this translate will release with the next version
of pgadmin III.thanks. how can i submit this translate-- 我渴望平静，风却给了我涟漪
I'd like to contribute to localize the application to italian language.
Do you want my help??
I wait your reply.
Michele
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Dear Michele.
Italian is no longer maintained and is long.
Please contribute. We are welcome always.:-)
http://www.pgadmin.org/translation.php
Regards,
Hiroshi Saito
From: "Michele Pigozzo
> I'd like to contribute to localize the application to italian language.
> Do you want my help??
>
>
* Magnus Hagander ([EMAIL PROTECTED]) wrote:
> ODBC and Kerberos works just fine, if you use the 8.1 ODBC driver. I use
> it all the time :)
That's what I had heard, I just havn't gotten it working yet myself. :)
Believe me when I say that I *really* want to have it working though;
this postgres->
-Original Message-
From: Stephen Frost [mailto:[EMAIL PROTECTED]
Sent: Fri 12/23/2005 2:42 PM
To: Martijn van Oosterhout
Cc: Greg Stark; Tom Lane; Christopher Kings-Lynne; Andrew Dunstan; Peter
Eisentraut; pgsql-hackers@postgresql.org; Andreas Pflug; Dave Page
Subject: Re: [HACKERS
> There's also Kerberos, which I'm happy to say seems to be
> getting more and more use. I'd really like to get ODBC
> Kerberos working, at least with MIT kerberos and then maybe
> someday (if I can manage to get it
> working...) setup some cross-realm stuff with the Windows AD and SSPI
> (iir
Stephen Frost wrote:
Is it actually doing challenge-response where the challenge is different
each time?
The docs say:
AuthenticationMD5Password
The frontend must now send a PasswordMessage containing the password
encrypted via MD5, using the 4-character salt specified in the
* Martijn van Oosterhout (kleptog@svana.org) wrote:
> On Fri, Dec 23, 2005 at 09:42:44AM -0500, Stephen Frost wrote:
> > * Martijn van Oosterhout (kleptog@svana.org) wrote:
> > > This isn't the first time this has been explained, but:
> > >
> > > With password encryption you essentially have two o
On Fri, Dec 23, 2005 at 09:42:44AM -0500, Stephen Frost wrote:
> * Martijn van Oosterhout (kleptog@svana.org) wrote:
> > This isn't the first time this has been explained, but:
> >
> > With password encryption you essentially have two options:
> >
> > - Server knows password, use challenge-respon
On 23 Dec 2005 09:12:52 -0500, Greg Stark <[EMAIL PROTECTED]> wrote:
>
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> > > AndrewSN can't post at the moment, but asked me to post this for him:
> > > "Knowing the md5 hash is enough to authenticate v
* Martijn van Oosterhout (kleptog@svana.org) wrote:
> On Fri, Dec 23, 2005 at 09:12:52AM -0500, Greg Stark wrote:
> > Eh? Just because you know everything the postmaster does doesn't mean you
> > can't be stopped. In the traditional unix password file scheme the crypt
> > string is public knowledge
On Fri, Dec 23, 2005 at 09:12:52AM -0500, Greg Stark wrote:
> Eh? Just because you know everything the postmaster does doesn't mean you
> can't be stopped. In the traditional unix password file scheme the crypt
> string is public knowledge but it's not enough to log in. You need the
> original pass
Tom Lane <[EMAIL PROTECTED]> writes:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> > AndrewSN can't post at the moment, but asked me to post this for him:
> > "Knowing the md5 hash is enough to authenticate via the 'md5' method in
> > pg_hba.conf, even if you don't know the original pa
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> AndrewSN can't post at the moment, but asked me to post this for him:
> "Knowing the md5 hash is enough to authenticate via the 'md5' method in
> pg_hba.conf, even if you don't know the original password.
If you know the md5 hash, you know eve
So, can I specify the password to pg_connect() as
'md5127349123742342344234'?
Certainly not. We'd hardly be worrying about obscuring the original
password if the encrypted version were enough to get in with.
AndrewSN can't post at the moment, but asked me to post this for him:
"Knowing the m
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> So, can I specify the password to pg_connect() as
> 'md5127349123742342344234'?
Certainly not. We'd hardly be worrying about obscuring the original
password if the encrypted version were enough to get in with.
regards
Where are we on this? In general I agree with Tom, but I have no time to
do the work. Unless someone has an immediate implementation, I suggest
that pro tem we add pg_md5_encrypt to src/interfaces/libpq/exports.txt,
which is the minimum needed to unbreak Windows builds, while this gets
sorted o
I wrote:
> I had forgotten that the Windows build is broken. I'll see what I can
> do with throwing together the cleaner-API function.
Done, but I noticed that the change to createuser has arguably broken
it; at least we need to change the docs. To wit, the docs say
-E
--encrypted
Encrypts
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Where are we on this? In general I agree with Tom, but I have no time to
> do the work. Unless someone has an immediate implementation, I suggest
> that pro tem we add pg_md5_encrypt to src/interfaces/libpq/exports.txt,
> which is the minimum needed t
Tom Lane wrote:
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
So it appears that pg_md5_encrypt is not officially exported from libpq.
Does anyone see a problem with adding it to the export list and the
header file?
Is it different to normal md5? How is this helpful to
Martijn van Oosterhout wrote:
-- Start of PGP signed section.
> On Wed, Dec 21, 2005 at 02:51:46PM -0500, Bruce Momjian wrote:
> > If you add a version number to the Win32 libpq name, you have to update
> > any command-line compile tools that mention libpq after an upgrade. The
> > Unix linker kno
IIRC the whole point of this exercise was to avoid passing the password
to the server in the first place. Unless you are talking about a PHP
md5() password of course ...
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ig
On Wed, Dec 21, 2005 at 02:51:46PM -0500, Bruce Momjian wrote:
> If you add a version number to the Win32 libpq name, you have to update
> any command-line compile tools that mention libpq after an upgrade. The
> Unix linker knows about version numbers, but the Win32 linker doesn't,
> so adding ve
On 12/21/05, Bruce Momjian wrote:
> Andreas Pflug wrote:
> > Martijn van Oosterhout wrote:
> >
> > >
> > > So it's only an issue if you have a policy of removing old versions of
> > > libpq on upgrades... I'm not sure what's "best practice" on windows in
> > > this area.
> >
> > When removing the
Andreas Pflug wrote:
> Martijn van Oosterhout wrote:
>
> >
> > So it's only an issue if you have a policy of removing old versions of
> > libpq on upgrades... I'm not sure what's "best practice" on windows in
> > this area.
>
> When removing the application (in this case: pgsql), you'd remove th
> -Original Message-
> From: Christopher Kings-Lynne [mailto:[EMAIL PROTECTED]
> Sent: 20 December 2005 01:33
> To: Dave Page
> Cc: Tom Lane; Peter Eisentraut; pgsql-hackers@postgresql.org;
> Andreas Pflug
> Subject: Re: [HACKERS] [pgadmin-hackers] Client-side p
I've already implemented this in phpPgAdmin trivially using the md5()
function. I can't be bothered using a C library function :D
IIRC the whole point of this exercise was to avoid passing the password
to the server in the first place. Unless you are talking about a PHP
md5() password of cours
Christopher Kings-Lynne wrote:
> By the way,
>
> I've already implemented this in phpPgAdmin trivially using the md5()
> function. I can't be bothered using a C library function :D
IIRC the whole point of this exercise was to avoid passing the password
to the server in the first place. Unless
pher Kings-Lynne
Cc: Peter Eisentraut; pgsql-hackers@postgresql.org; Andreas
Pflug; Dave Page
Subject: Re: [HACKERS] [pgadmin-hackers] Client-side password
encryption
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
So it appears that pg_md5_encrypt is not officially
exported fro
Tom Lane wrote:
Martijn van Oosterhout writes:
Are there any reasons why we shouldn't change the libname with every
release like for UNIX? I can't think of any, but you never know...
Surely that cure is far worse than the disease. You'd be trading a
might-break risk (app using new f
Peter Eisentraut said:
>
> So it appears that pg_md5_encrypt is not officially exported from
> libpq. Does anyone see a problem with adding it to the export list
> and the header file?
>
Well, these changes have broken the windows build, so something needs to
change.I don't see a reason in pr
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 19 December 2005 15:00
> To: Martijn van Oosterhout
> Cc: Dave Page; Christopher Kings-Lynne; Peter Eisentraut;
> pgsql-hackers@postgresql.org; Andreas Pflug
> Subject: Re: [HACKERS] [pgadmin
Martijn van Oosterhout writes:
> Are there any reasons why we shouldn't change the libname with every
> release like for UNIX? I can't think of any, but you never know...
Surely that cure is far worse than the disease. You'd be trading a
might-break risk (app using new function will fail if used
> -Original Message-
> From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: 19 December 2005 14:50
> To: Dave Page; Martijn van Oosterhout
> Cc: Tom Lane; Christopher Kings-Lynne; Peter Eisentraut;
> pgsql-hackers@postgresql.org; Andreas Pflug
> Subject: R
> > Yes.
> > If FooApp is compiled against 8.0, it will then be unable to run if
> > you upgrade libpq to 8.1. IIRC on Unix it will "fall
> forward" to the
> > new version if it's just a minor version upgrade (correct me if I'm
> > wrong).
> > On windows, it will break with an ugly dialog box.
> -Original Message-
> From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: 19 December 2005 12:07
> To: Martijn van Oosterhout; Dave Page
> Cc: Tom Lane; Christopher Kings-Lynne; Peter Eisentraut;
> pgsql-hackers@postgresql.org; Andreas Pflug
> Subject: R
Martijn van Oosterhout wrote:
So it's only an issue if you have a policy of removing old versions of
libpq on upgrades... I'm not sure what's "best practice" on windows in
this area.
When removing the application (in this case: pgsql), you'd remove that
old lib as well if it's the only app u
On Mon, Dec 19, 2005 at 01:07:26PM +0100, Magnus Hagander wrote:
> If FooApp is compiled against 8.0, it will then be unable to run if you
> upgrade libpq to 8.1. IIRC on Unix it will "fall forward" to the new
> version if it's just a minor version upgrade (correct me if I'm wrong).
> On windows, i
> > > As for Windows DLL hell, I don't know a lot about that, but if
> > > that's such a problem, why didn't the original creators of the
> > > windows port stick the version number in there from the start. On
> > > UNIX, libpq is half versioned (the library is, but not
> the symbols)
> > > so
> -Original Message-
> From: Martijn van Oosterhout [mailto:[EMAIL PROTECTED]
> Sent: 19 December 2005 10:42
> To: Dave Page
> Cc: Tom Lane; Christopher Kings-Lynne; Peter Eisentraut;
> pgsql-hackers@postgresql.org; Andreas Pflug
> Subject: Re: [HACKERS] [pgadmin
On Mon, Dec 19, 2005 at 10:32:03AM -, Dave Page wrote:
>
> > As for Windows DLL hell, I don't know a lot about that, but if that's
> > such a problem, why didn't the original creators of the windows port
> > stick the version number in there from the start. On UNIX, libpq is
> > half versioned
> -Original Message-
> From: Martijn van Oosterhout [mailto:[EMAIL PROTECTED]
> Sent: 19 December 2005 09:38
> To: Dave Page
> Cc: Tom Lane; Christopher Kings-Lynne; Peter Eisentraut;
> pgsql-hackers@postgresql.org; Andreas Pflug
> Subject: Re: [HACKERS] [pgadmin
On Mon, Dec 19, 2005 at 09:16:19AM -, Dave Page wrote:
> > > > Something like
> > > > char *pg_gen_encrypted_passwd(const char *passwd, const
> > > > char *user)
> > > > with malloc'd result (or NULL on failure) seems more future-proof.
> > If programs are really worried about it, the
> -Original Message-
> From: Martijn van Oosterhout [mailto:[EMAIL PROTECTED]
> Sent: 19 December 2005 08:59
> To: Dave Page
> Cc: Tom Lane; Christopher Kings-Lynne; Peter Eisentraut;
> pgsql-hackers@postgresql.org; Andreas Pflug
> Subject: Re: [HACKERS] [pgadmin
On Mon, Dec 19, 2005 at 08:51:23AM -, Dave Page wrote:
> > Something like
> > char *pg_gen_encrypted_passwd(const char *passwd, const
> > char *user)
> > with malloc'd result (or NULL on failure) seems more future-proof.
>
> Changing the API is likely to cause fun on Windows for new apps
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 19 December 2005 05:37
> To: Christopher Kings-Lynne
> Cc: Peter Eisentraut; pgsql-hackers@postgresql.org; Andreas
> Pflug; Dave Page
> Subject: Re: [HACKERS] [pgadmin-hackers] Client-side p
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> So it appears that pg_md5_encrypt is not officially exported from libpq.
>> Does anyone see a problem with adding it to the export list and the
>> header file?
> Is it different to normal md5? How is this helpful to the phpPgAdmin
> proje
So it appears that pg_md5_encrypt is not officially exported from libpq.
Does anyone see a problem with adding it to the export list and the
header file?
Is it different to normal md5? How is this helpful to the phpPgAdmin
project?
Chris
---(end of broadcast)-
Andreas Pflug wrote:
> Dave Page wrote:
> > So did you just rip it from there into psql? I don't see it in the
> > list of libpq exports so if thats not the case, on Windows at least
> > we'll need to change the api, and possibly the dll name as well to
> > avoid any compatibility issues.
>
> And
I noticed a typo in hints/conn-hba.html
The second internal ip adres missed a '.'
You're invited to make your comments on the hints: are these correct, is
there something missing or misleading?
Cheers,
--
^(B(astia{2}n)?)(\s)?(W(ak{2}ie)?)$
Thanks - fix committed to svn.
Regards, Dave
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bastiaan
WakkieSent: 03 October 2005 17:04To: Andreas
PflugCc: PostgreSQL-development; pgadmin-hackers;
pgsql-admin@postgresql.orgSubject: Re: [pgadmin-hackers
On Mon, Oct 03, 2005 at 02:16:37AM +0200, Andreas Pflug wrote:
> In-time for PostgreSQL 8.1 gold, The pgAdmin Developer Team will
> release pgAdmin III V1.4, which has a new Guru hint feature that
> tries to give users helpful hints on typical beginner's pitfalls.
>
> The current set of hints is a
In-time for PostgreSQL 8.1 gold, The pgAdmin Developer Team will release
pgAdmin III V1.4, which has a new Guru hint feature that tries to give
users helpful hints on typical beginner's pitfalls.
The current set of hints is at
http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/trunk/pgadmin3/docs/en_US
When grilled further on (29 Feb 2004 08:46:36 -0800),
[EMAIL PROTECTED] (Hammer) confessed:
> Quick one:
> Anyone know how to use Putty to open a connection up under SSH which
> will allow pgAdmin III to connect to a postgresql database ie. Only
> access to server postgresql is on is via ssh.
>
When grilled further on (29 Feb 2004 08:46:36 -0800),
[EMAIL PROTECTED] (Hammer) confessed:
> Quick one:
> Anyone know how to use Putty to open a connection up under SSH which
> will allow pgAdmin III to connect to a postgresql database ie. Only
> access to server postgresql is on is via ssh.
>
Quick one:
Anyone know how to use Putty to open a connection up under SSH which
will allow pgAdmin III to connect to a postgresql database ie. Only
access to server postgresql is on is via ssh.
Thanks
Hammer
---(end of broadcast)---
TIP 7: don't for
David Sigeti wrote:
At 12:21 PM 12/10/2003 +0100, Andreas Pflug wrote:
David Sigeti wrote:
I am using pgadminIII 1.0.2 with PostgreSQL 7.4 under W2K SP4 and
Cygwin (current as of 2 or 3 weeks ago). The server is running
locally.
If I attempt to add an column of type serial or bigserial to a
Dave Page wrote:
/* A Bison parser, made by GNU Bison 1.875. */
Given that this file appears to be produced *by* Bison, and given this
exception:
/* As a special exception, when this file is copied by Bison into a
Bison output file, you may use that output file without restriction.
This sp
Frank Schoep writes:
> I'd be willing to write a Dutch translation for pgAdmin III,
For matters concerning pgAdmin III, please see its web site
http://www.pgadmin.org/pgadmin3/; there are separate mailing lists for it.
You're also invited to provide a translation for the core of PostgreSQL;
see
-
> From: Frank Schoep [mailto:[EMAIL PROTECTED]
> Sent: 31 August 2003 10:49
> To: PostgreSQL Hackers
> Subject: [HACKERS] pgAdmin III translation: Dutch
>
>
> Hello there,
>
> I'd be willing to write a Dutch translation for pgAdmin III,
> if you are
>
Hello there,
I'd be willing to write a Dutch translation for pgAdmin III, if you are
interested in it. I'll give you the language details in advance:
English-language-name: Dutch
Native-language-name: Nederlands
Please let me know if it'd be a good thing to do and I'll start on it whenever
I fi
On Thursday 03 July 2003 12:32, A. van Roggen wrote:
> If you ever have read the instruction books for e.g. early VCR
> recorders, translated from the original Japanese to English, you will know
> exactly what I mean. Proper translation is not an easy job, and
> volunteers from another branch of t
> -Original Message-
> From: A. van Roggen [mailto:[EMAIL PROTECTED]
> Sent: 03 July 2003 11:33
> To: Dave Page
> Cc: [EMAIL PROTECTED];
> [EMAIL PROTECTED];
> [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] [GENERAL] pgAdmin III - Call
> fo
As many of you already know, pgAdmin is a widely used Open Source GUI
Management tool for PostgreSQL, similar to DB2's Control Center or SQL
Server's Enterprise Manager.
We are currently working on the next generation pgAdmin III, with the
aim of releasing it at approximately the same time as Pos
Since you're using wxWindows, I *HIGHLY* recommend obtaining a license
to wxDesigner from http://www.roebling.de/. It allows for very rapid
GUI design. It also understands various sizers and makes it SOOO much
easier to make use of them. Once you understand sizers, you'll love
them but they are
> -Original Message-
> From: Greg Copeland [mailto:greg@;copelandconsulting.net]
> Sent: 30 October 2002 01:08
> To: Dave Page
> Subject: Re: [HACKERS] Request for supported platforms
>
>
> C++? Really? What GUI toolkit is being used?
>
> Just curious.
wxWindows. The CVS is online
1 - 100 of 104 matches
Mail list logo
