[EMAIL PROTECTED] wrote:
Dave Page wrote:
All is not necessarily lost however - it strike me that we might be able
to use the STC control instead of a rich textbox (thats the one we use
for the SQL input fields). I'll look into it
Unfortunately that doesn't seem to be feasible :-(
Dave Page wrote:
> All is not necessarily lost however - it strike me that we might be able
> to use the STC control instead of a rich textbox (thats the one we use
> for the SQL input fields). I'll look into it
Unfortunately that doesn't seem to be feasible :-(
Regards, Dave.
--
Erwin Brandstetter wrote:
> Dave Page wrote:
>> The problem is though, that it remains the underlying controls that
>> are doing the copy and the paste operations so we still have no way in
>> pgAdmin to filter it out. You can actually test this by pasting using
>> the button to do it - that does u
Dave Page wrote:
The problem is though, that it remains the underlying controls that
are doing the copy and the paste operations so we still have no way in
pgAdmin to filter it out. You can actually test this by pasting using
the button to do it - that does use our code which ensures it pastes
Erwin Brandstetter wrote:
We have been discussing this before. I think there is a
misunderstanding involved. The newline is not appended at paste time,
it is appended in the text field in the edit grid BEFORE copying.
>
You can de-select the appended non-printing character in the text
field in
Sorry, I was in the process of editing my post, when the
groups.google.com decided to interpret " -" as my will to
send it. So the posting above is quite unfinished. ยง$%&/( interface! :
(
Anyway, here is what my finished posting would look like:
On Jul 19, 4:53 pm, [EMAIL PROTECTED] (Dave Page) wr
On Jul 19, 4:53 pm, [EMAIL PROTECTED] (Dave Page) wrote:
> Kieran McCusker wrote:
(...)
> > Copy and paste from edit grid adds a newline
> > ===
>
> > If you double click on a text field in the grid and do ctrl-c then paste
> > the result into another text field you get a ne
Kieran McCusker wrote:
> Dave
>
> show search_path returns : "$user",public
Ah-ha - I tested on EnterpriseDB which misses the quotes (which I guess
were added in PostgreSQL at some point). I've changed the code to allow
for possible quotes - will commit shortly.
Thanks for the report.
Regards,
Kieran McCusker wrote:
> Dave
>
> I am logged on as user portal and there is a schema portal, select
> current_schemas(false) reports {portal,public} my default schema is public.
> Does this give you a clue?
What does
show search_path;
return (exactly - spelling, case, quoting etc)?
Regards, D
Kieran McCusker wrote:
> Hi
>
> Both these issues are also present in the 1.6 series :-
>
> public schema prefix not added to any scripts
> ===
>
> This exists in 1.6 as well, but if you have a login that is also the
> name of a schema and you edit a public anything using
Hi
Both these issues are also present in the 1.6 series :-
public schema prefix not added to any scripts
===
This exists in 1.6 as well, but if you have a login that is also the
name of a schema and you edit a public anything using CREATE script then
"public." is not a
11 matches
Mail list logo
