Dave Page wrote:
I don't mean change the schema name, I mean change the design of the
schema (ie. add a column, or remove a table or something). The schema
name should always be pgagent so there should be no migration issues.
oh. I misunderstood. :(
Thanks & Regards,
Ashesh Vashi
Enterprise
On Fri, Dec 19, 2008 at 10:22 AM, Ashesh Vashi
wrote:
> Dave Page wrote:
>
> On Fri, Dec 19, 2008 at 9:31 AM, Ashesh Vashi
> wrote:
>
> * Add an SQL function pgagent_schema_version() which returns an int
> (with a value of 3 for this version - we'll bump the package to
> 3.0.0).
>
> I thought o
Dave Page wrote:
On Fri, Dec 19, 2008 at 9:31 AM, Ashesh Vashi
wrote:
* Add an SQL function pgagent_schema_version() which returns an int
(with a value of 3 for this version - we'll bump the package to
3.0.0).
I thought of this options too. :)
Shouldn't we return a text instead of integer x
On Fri, Dec 19, 2008 at 9:31 AM, Ashesh Vashi
wrote:
> * Add an SQL function pgagent_schema_version() which returns an int
> (with a value of 3 for this version - we'll bump the package to
> 3.0.0).
>
> I thought of this options too. :)
> Shouldn't we return a text instead of integer x.x.x supp
Hi Dave Page,
Dave Page wrote:
I haven't tested fully at this stage, just eyeball reviewed the code,
made sure it builds (on Windows) and checked out the UI. First
impression is that it's well thought out and nicely implemented.
Thanks
- The pgTable::HasColumn() static function seems like an
On Thu, Dec 18, 2008 at 12:25 PM, Ashesh Vashi
wrote:
> Hi All,
>
> As per my discussion with Dave Page:
[for those that haven't realised, Ashesh is one of EDB's crack
programmers and is very kindly helping me out with some of the pgAdmin
work I don't currently have time for].
> - Add support fo
