| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Nikhil S <nixmisc(at)gmail(dot)com>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: pgAdmin III: error while browsing schema of PG database |
| Date: | 2011-02-08 10:01:23 |
| Message-ID: | AANLkTinEuj6Kob9=Kb_prz9pac4RZ0d-n2=c_oJXCTFS@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On 2/8/11, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Tue, Feb 8, 2011 at 08:22, Nikhil S <nixmisc(at)gmail(dot)com> wrote:
>>
>>
>>>
>>> Well, the SQL does get fired against a PG database in the EDBAS mode for
>>> me. I too was puzzled about the minimum version check being EDBAS
>>> specific.
>>>
>>
>> Just checked. The version checker function checks for the version number
>> and
>> also for a bool which is set to true in EDBAS mode. So yeah, this will not
>> be repro in pure Postgresql mode operations. Sorry for indicating so. But
>> the issue defo comes if you try to browse a PG database in EDBAS mode.
>
> Why would you browse a PG database in EDBAS mode? Isn't there a whole
> lot of other things that would break in that case as well?
>
> Or maybe I'm misunderstanding what you mean with "EDBAS mode"?
>
He means when edbas is running in PG mode instead of Oracle mode.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-02-08 10:05:02 | Re: pgAdmin III: error while browsing schema of PG database |
| Previous Message | Magnus Hagander | 2011-02-08 09:51:29 | Re: pgAdmin III: error while browsing schema of PG database |