From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Dan Shoubridge <dan(dot)shoubridge(at)autovhc(dot)co(dot)uk> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Feature Request for Debugging SQL in PGAdmin3 when SQL contains variables |
Date: | 2010-11-16 12:43:28 |
Message-ID: | 4CE27C70.9010605@lelarge.info |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Le 16/11/2010 13:34, Guillaume Lelarge a écrit :
> Le 16/11/2010 13:14, Dan Shoubridge a écrit :
>> Originally from SQL Server background, there is one feature that I am
>> missing and would save developers hours of time.
>>
>> In SQL Server I could copy sql code out of an application and paste it into
>> SSMS, declare & assign vars that exist in the sql and run - great debugging
>> scenario.
>> e.g. (please note I am rusty and syntax may be incorrect)
>>
>> declare @x as varchar(10)
>> set @x = 'abc'
>> select * from sometable where somefield = @x
>>
>> It would be amazing if simular functionality could be built into in pgadmin3
>> (NpgSQL uses : instead of @) where I can just drop my sql (params & all)
>> into the query window.
>>
>> I realise you can create pgscript, but it doesn't achieve the above...
>> Currently I have a peice of sql someone has written that has 3 unique
>> varibles in it which are used around 7 times each...
>>
>
> And? I don't see why pgscript can't do that. The example you give is
> certainly doable with pgscript.
>
Just for the record, the above script looks like this in pgscript:
declare @x;
set @x = 'abc';
select * from sometable where somefield = '@x';
And it works.
--
Guillaume
http://www.postgresql.fr
http://dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Shoubridge | 2010-11-16 12:49:44 | Re: Feature Request for Debugging SQL in PGAdmin3 when SQL contains variables |
Previous Message | Guillaume Lelarge | 2010-11-16 12:34:59 | Re: Feature Request for Debugging SQL in PGAdmin3 when SQL contains variables |