On Wed, Apr 7, 2010 at 9:28 PM, Gaetan beaulieu wrote:
> Hi!
> I found a little problem with the CTRL-Z in the SQL command editor.
>
> I have two files, each containing several SQL queries. sql_01.sql and
> sql_02.sql.
>
> I get the first file sql_01.sql from the menu, I run and everything is fine
Hi!
I found a little problem with the CTRL-Z in the SQL command editor.
I have two files, each containing several SQL queries. sql_01.sql and
sql_02.sql.
I get the first file sql_01.sql from the menu, I run and everything is fine.
I get the second file from the menu in the same edit window
Le 07/04/2010 10:47, Kieran McCusker a écrit :
> [...]
> Sorry if this has been raised before but the following function will not
> be reverse engineered correctly - It will be changed into a setof return
> which will break anything expecting organisation_id.
>
It's already fixed in the SVN versi
On Wed, Apr 7, 2010 at 4:21 PM, Olivier Bouiron wrote:
> Hi evryone.
> I would like to know if the pgpass file will be encrypted in a futur version
> of pgadmin.
the pgpass file is a function of PostgreSQL, not pgadmin.
> It's not a bug but it could be a good thing to do that one day (and I th
Hi evryone.
I would like to know if the pgpass file will be encrypted in a futur
version of pgadmin.
It's not a bug but it could be a good thing to do that one day (and I
think it's not very difficult, isn't it?).
Regards
--
Olivier Bouiron
Institut Sainte Catherine
1750, chemin du lavarin
Hi
Sorry if this has been raised before but the following function will not
be reverse engineered correctly - It will be changed into a setof return
which will break anything expecting organisation_id.
CREATE OR REPLACE FUNCTION public.t() RETURNS TABLE (organisation_id
integer) AS
$$
sele
