Another one noticed in the MERGE RETURNING patch -- this allows PL/Tcl
to execute MERGE (i.e., don't fail when SPI returns SPI_OK_MERGE). I'm
not sure if anyone uses PL/Tcl anymore, but it's a trivial fix,
probably not worth a regression test case.
Regards,
Dean
diff --git a/src/pl/tcl/pltcl.c b
On Mon, 20 Feb 2023 at 19:39, Tom Lane wrote:
>
> Ugh. Grepping around, it looks like pltcl_process_SPI_result
> is missing a case for SPI_OK_MERGE as well.
>
Yes, I was about to post a patch for that too. That's the last case
that I found, looking around.
Regards,
Dean
ted, I don't think there's
much point in adding a regression test case for it though.
Regards,
Dean
diff --git a/doc/src/sgml/spi.sgml b/doc/src/sgml/spi.sgml
new file mode 100644
index 7581661..651930a
--- a/doc/src/sgml/spi.sgml
+++ b/doc/src/sgml/spi.sgml
@@ -438,6 +438,15 @@ typedef str
(and hence non-empty withCheckOptionLists to
initialise).
So I think we need something like the attached.
Regards,
Dean
diff --git a/src/backend/executor/execPartition.c b/src/backend/executor/execPartition.c
new file mode 100644
index 651ad24..fd6ca8a
--- a/src/backend/executor/execPartition.c
for a normal update), and then ExecMergeMatched() will
update it again.
I think the best fix is to have ExecMergeMatched() pass canSetTag =
false to ExecUpdateAct(), so that ExecMergeMatched() takes
responsibility for updating estate->es_processed in all cases.
Regards,
Dean
diff --git a/src/
ations. I'd
need to see some more realistic test results, or some real evidence of
palloc/pfree causing significant overhead in a numeric computation.
Regards,
Dean
diff --git a/src/backend/utils/adt/numeric.c b/src/backend/utils/adt/numeric.c
new file mode 100644
index a83feea..c937eaf
--- a/src/back
Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: fb48549c51eda1cc99d256d1cfbce7576883b9f5
https://github.com/WebKit/WebKit/commit/fb48549c51eda1cc99d256d1cfbce7576883b9f5
Author: Dean Jackson
Date: 2023-02-17 (Fri, 17 Feb 2023)
Changed paths:
M
Each time a menu would change scenes, a new set of ListChangeListeners would be
added to the items in the menu. The bigger problem however is that these list
change listeners have a strong reference to the scene which is potentially a
much bigger leak.
The first commit was more
Package: hplip
Version: 3.22.10+dfsg0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: smit...@hush.com
Dear Maintainer,
* What led up to the situation?
The cups hplip suddenly stopped working and initiated the plugin
download, which failed.
-- Package-specific
Package: hplip
Version: 3.22.10+dfsg0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: smit...@hush.com
Dear Maintainer,
* What led up to the situation?
The cups hplip suddenly stopped working and initiated the plugin
download, which failed.
-- Package-specific
Package: hplip
Version: 3.22.10+dfsg0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: smit...@hush.com
Dear Maintainer,
* What led up to the situation?
The cups hplip suddenly stopped working and initiated the plugin
download, which failed.
-- Package-specific
but
not backup or change things like the welcome screen etc.
Almost thing my utility might be corrupt?
It is communicating with the K3, which has db9 serial.
Thanks in advance 73
Dean K2WW
__
Elecraft mailing list
Home: http://mailman.qth.net
I got a quote from "Fix Leaky Boats” on replacing windows and frames (fixed /
non-opening) on my 1980 34' two years ago and it was about $2,000 Canadian. I
didn’t proceed but that might give you an idea of pricing. I’ve heard great
things about their products.
Dean
> On Feb 9, 2023,
https://bugs.kde.org/show_bug.cgi?id=465490
--- Comment #2 from Zero Dean ---
Created attachment 156091
--> https://bugs.kde.org/attachment.cgi?id=156091=edit
A mockup of a dual gallery setup allowing users to see a separate gallery of
rated items from that particular folder/gallery
A moc
https://bugs.kde.org/show_bug.cgi?id=465490
Bug ID: 465490
Summary: Feature request
Classification: Applications
Product: digikam
Version: unspecified
Platform: Other
OS: Other
Status: REPORTED
Package: linux-headers-6.1.0-3-amd64
Version: 6.1.8-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in
the past)
X-Debbugs-Cc: smit...@hush.com
Dear Maintainer,
*** Reporter,
Package: linux-headers-6.1.0-3-amd64
Version: 6.1.8-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in
the past)
X-Debbugs-Cc: smit...@hush.com
Dear Maintainer,
*** Reporter,
Hello!
I am still experiencing this bug. Here is the log from my latest
attempt to update:
=DKMS
make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.1 for kernel
6.1.0-3-amd64 (x86_64)
Tue Feb 7 08:47:34 AM PST 2023
make: Entering
Hello!
I am still experiencing this bug. Here is the log from my latest
attempt to update:
=DKMS
make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.1 for kernel
6.1.0-3-amd64 (x86_64)
Tue Feb 7 08:47:34 AM PST 2023
make: Entering
On Mon, 23 Jan 2023 at 16:54, Dean Rasheed wrote:
>
> On Sun, 22 Jan 2023 at 19:08, Alvaro Herrera wrote:
> >
> > Regarding mas_action_idx, I would have thought that it belongs in
> > MergeAction rather than MergeActionState. After all, you determine i
On Sat, 21 Jan 2023 at 14:18, Ted Yu wrote:
>
> On Sat, Jan 21, 2023 at 3:05 AM Dean Rasheed wrote:
>>
>> Rebased version, following 8eba3e3f02 and 5d29d525ff.
>>
Another rebased version attached.
> In transform_MERGE_to_join :
>
> +
out/soong/build.ninja" after simply running "touch" on one Android.bp file
in vendor/ directory.
On Thursday, February 2, 2023 at 2:29:06 PM UTC+11 Dean Wheatley wrote:
> Is there a better/faster way to develop Android.bp in the AOSP tree than
> waiting for the man
Per
https://cs.android.com/android/platform/superproject/+/master:build/soong/android/variable.go;bpv=1;bpt=1
, static_libs can be declared in debuggable only, not eng. What is the
reason for restricting this? I'd like to include static_libs for eng build
only.
--
--
You received this
Thank you to all The Parks and Rec. people who were involved in putting the
Coffee House back on!!!
It was fantastic
Dean
On Sun, Feb 5, 2023 at 4:38 PM Scott Clary wrote:
> That was a blast! So glad it's back! Thank you to Lindsay and everyone
> else for all your dedicated hard work!
&g
OK - real story. Working as an L2 support tech for a well known
software company. New release of the product required a new SVC because
an area in the F1 DSCB that was previously unused by IBM was now being
used - so that critical bit of data had to be moved to a new unused
area. The
On Thu, 2 Feb 2023 at 22:40, Peter Eisentraut
wrote:
>
> On 31.01.23 17:09, Dean Rasheed wrote:
> > On Tue, 31 Jan 2023 at 15:28, Peter Eisentraut
> > wrote:
> >>
> >> Did you have any thoughts about what to do with the float types? I
> >> gu
is allowed between any 2 digits, or immediately
after the base prefix indicator of non-decimal integers, per SQL:202x
draft.
Peter Eisentraut and Dean Rasheed
Discussion:
https://postgr.es/m/84aae844-dc55-a4be-86d9-4f0fa405cc97%40enterprisedb.com
Branch
--
master
Details
---
https
ch to v14, where it was introduced.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https://postgr.es/m/CAEZATCW8gXgW0tgPxPgHDPhVX71%2BSWFRkhnXy%2BTfGDsKLepu2g%40mail.gmail.com
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/86bfbeab4f439ad527318d9edeb3c71ea4
ch to v14, where it was introduced.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https://postgr.es/m/CAEZATCW8gXgW0tgPxPgHDPhVX71%2BSWFRkhnXy%2BTfGDsKLepu2g%40mail.gmail.com
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/4f74741a5cea38228fdb0fb2967fa2137e
ch to v14, where it was introduced.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https://postgr.es/m/CAEZATCW8gXgW0tgPxPgHDPhVX71%2BSWFRkhnXy%2BTfGDsKLepu2g%40mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/b2d47928908d7a99b8e39198d0e8e9e0cb2b024b
On Fri, 3 Feb 2023 at 01:18, Tom Lane wrote:
>
> Dean Rasheed writes:
>
> > 1). It doesn't work if log10val2 < 0, because then m < 0, and it
> > doesn't multiply by the remainder. And it then throws an overflow
> > error, because result.dscale comes out wrong w
or 6, but it's definitely a
bug waiting to happen.
This was added by a2da77cdb4 ("Change return type of EXTRACT to
numeric"), so it only goes back as far as v14.
After hacking on it for a while, I ended up with the attached.
Regards,
Dean
diff --git a/src/backend/utils/adt/numeric.c b/src/bac
cause I forgot, so the
reminder would be useful.
And as someone who runs pgindent regularly, I think this will be a net
time saver, since I won't have to skip over other unrelated indent
changes all the time.
Regards,
Dean
On Tue, 31 Jan 2023 at 21:59, Joel Jacobson wrote:
>
> Nice, you managed to simplify it even further.
> I think the comment and the code now are crystal clear together.
>
> I've tested it successfully, test report attached.
>
Cool. Thanks for testing.
Committed.
Regards,
Dean
Ensure that numeric.c compiles with other NBASE values.
As noted in the comments, support for different NBASE values is really
only of historical interest, but as long as we're keeping it, we might
as well make sure that it compiles.
Joel Jacobson
Discussion:
the computation in that case.
Joel Jacobson and Dean Rasheed
Discussion:
https://postgr.es/m/06712c29-98e9-43b3-98da-f234d81c6e49%40app.fastmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/0736fc1ceb0659a9f73699910ac56603336daeee
Modified Files
Is there a better/faster way to develop Android.bp in the AOSP tree than
waiting for the many (> 60) seconds it takes to "analyzing Android.bp files
and generating ninja file at out/soong/build.ninja" after any change to any
Android.bp file in the tree?
--
--
You received this message
wine_audit VALUES('U', now(), oldrec, newrec);
END LOOP;
CLOSE oldcur;
CLOSE newcur;
END;
END IF;
RETURN NULL;
END;
$$;
though it would be nicer if there was a way to do it in a single SQL statement.
Regards,
Dean
sweight = arg.weight * DEC_DIGITS / 2 + 1;
#else
if (arg.weight >= 0)
sweight = arg.weight * DEC_DIGITS / 2 + 1;
else
sweight = 1 - (1 - arg.weight * DEC_DIGITS) / 2;
#endif
Regards,
Dean
arily impact their performance.
Regards,
Dean
's not using the exact input decimal weight. So
my inclination is to leave the code as-is. It does guarantee that the
result has at least 16 significant digits, which is the intention.
Regards,
Dean
that could be relaxed, by allowing some generated
columns to be skipped for a MERGE without an INSERT action, but it's
not clear that it's worth the effort.
Noticed while investigating bug #17759. Back-patch to v15, where MERGE
was added.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https
that could be relaxed, by allowing some generated
columns to be skipped for a MERGE without an INSERT action, but it's
not clear that it's worth the effort.
Noticed while investigating bug #17759. Back-patch to v15, where MERGE
was added.
Dean Rasheed, reviewed by Tom Lane.
Discussion:
https
d DEC_DIGITS==1,
> since otherwise it's not possible to compile such DEC_DIGITS values
> due to the assert:
>
> StaticAssertDecl(lengthof(pow10) == DEC_DIGITS, "mismatch with
> DEC_DIGITS");
>
That might be worth doing, to ensure that the code still compiles for
other DEC_DIGITS/NBASE values. I'm not sure how useful that really is
anymore though. As the comment at the top says, it's kept mostly for
historical reasons.
Regards,
Dean
rge action list (it would be OK to skip
generated columns as long as the MERGE didn't contain an INSERT
action), but I don't think it's worth the extra effort / risk.
So I think we need the attached in HEAD and v15.
Regards,
Dean
diff --git a/src/backend/executor/nodeModifyTable.c b/src/backend/execu
On Wed, 25 Jan 2023 at 21:43, Peter Eisentraut
wrote:
>
> On 24.01.23 14:10, Dean Rasheed wrote:
> > I also think it might be useful for it to gain a couple of boolean options:
> >
> > 1). An option to output a signed value (defaulting to false, to
> > preserve the c
83648
(1 row)
SELECT pg_typeof(-0x8000);
pg_typeof
---
integer
(1 row)
Regards,
Dean
ing unsigned ints,
without resorting to abs() (yes, I'm aware that abs() is undefined for
INT_MIN).
Regards,
Dean
d. In particular, this
shouldn't need any changes to IndexStmt. I think the best approach
would be to just add a new function to backend_progress.c that offsets
a specified progress parameter by a specified amount, so that you can
just increment partitions_done by one or more, at the appropriate
points.
Regards,
Dean
ERROR: integer out of range
Part of the reason for implementing this in core would be to save
users from such easy-to-overlook bugs.
Regards,
Dean
(for integers only, since non-integers won't necessarily
terminate in hex, aren't accepted as inputs, and don't seem
particularly useful anyway). I don't think two's complement output
makes much sense for numeric, so perhaps it should only have the
prefix option, and always output signed hex strings.
Thoughts?
Regards,
Dean
On Tue, 24 Jan 2023 at 00:47, Ranier Vilela wrote:
>
> On 13.01.23 11:01, Dean Rasheed wrote:
> > So I'm feeling quite good about the end result -- I set out hoping not
> > to make performance noticeably worse, but ended up making it
> > significantly better.
> Hi
it. Perhaps start a new thread to gauge people's interest?
Regards,
Dean
On Wed, 4 Jan 2023 at 09:28, Dean Rasheed wrote:
>
> In addition, I think that strip_underscores() could then go away if
> numeric_in() were made to handle underscores.
>
> Essentially then, that would move all responsibility for parsing
> underscores and non-decimal intege
Add non-decimal integer support to type numeric.
This enhances the numeric type input function, adding support for
hexadecimal, octal, and binary integers of any size, up to the limits
of the numeric type.
Since 6fcda9aba8, such non-decimal integers have been accepted by the
parser as integer
RNING in an incompatible way in the future.
> Regarding mas_action_idx, I would have thought that it belongs in
> MergeAction rather than MergeActionState. After all, you determine it
> once at parse time, and it is a constant from there onwards, right?
>
Oh, yes that makes sense (and removes the need for a couple of the
executor changes). Thanks for looking.
Regards,
Dean
On Mon, 23 Jan 2023 at 15:55, Peter Eisentraut
wrote:
>
> On 13.01.23 11:01, Dean Rasheed wrote:
> > So I'm feeling quite good about the end result -- I set out hoping not
> > to make performance noticeably worse, but ended up making it
> > significantly better.
>
&
e testing, the gains look good to me, and I wasn't able
to find any cases where it made things slower, so I've gone ahead and
pushed it.
Regards,
Dean
bles.pdf
>
Thanks, that's a very useful reference.
(And I do indeed have one of those CPUs, which explains what I was seeing.)
Regards,
Dean
Optimise numeric division for 3 and 4 base-NBASE digit divisors.
On platforms with 128-bit integer support, introduce a new function
div_var_int64(), along the same lines as div_var_int() added in
d1b307eef2 for divisors with 1 or 2 base-NBASE digits, and use it to
speed up div_var() and
On Sun, 22 Jan 2023 at 15:41, Joel Jacobson wrote:
>
> On Sun, Jan 22, 2023, at 11:06, Dean Rasheed wrote:
> > Seems like a reasonable idea, with some pretty decent gains.
> >
> > Note, however, that for a divisor having fewer than 5 or 6 digits,
> > it's now sig
for all small divisors. So
the var2ndigits <= 2 case needs to come first.
The implementation of div_var_int64() should be in an #ifdef HAVE_INT128 block.
In div_var_int64(), s/ULONG_MAX/PG_UINT64_MAX/
Regards,
Dean
On Mon, 9 Jan 2023 at 17:44, Dean Rasheed wrote:
>
> On Mon, 9 Jan 2023 at 16:23, Vik Fearing wrote:
> >
> > Bikeshedding here. Instead of Yet Another WITH Clause, could we perhaps
> > make a MERGING() function analogous to the GROUPING() function that goes
> > wit
On Tue, 10 Jan 2023 at 14:43, Dean Rasheed wrote:
>
> Rebased version attached.
>
Rebased version, following 8eba3e3f02 and 5d29d525ff.
Regards,
Dean
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
new file mode 100644
index b87ad5c..1482ede
--- a/doc/src/sgml/mvcc.sgml
Knute: No, I haven't run Lilypond from the command line (I have enough
trouble using it with Frescobaldi 3.2)
Machine: Windows 10 Pro 64-bit, 16GB memory
LP version 2.24
Mike Dean
On Thu, Jan 19, 2023 at 12:15 PM Knute Snortum wrote:
> On Thu, Jan 19, 2023 at 9:01 AM Mike Dean wr
d4 r \bar ":|."
}
\score {
<<
\new ChordNames {
\set chordChanges = ##t
\harmonies
}
\new Voice = "one" { \melody }
>>
}
Mike Dean
t adding an ORDER BY clause changes the contents
of the rows returned, not just their order.
The trouble is, if we tried to fix that, we'd risk changing some other
behaviour that users may have come to rely on.
Regards,
Dean
changes to 3D plotting to
accommodate the pending update of the rgl package.
As always, all changes are listed in the News file.
Happy computing!
Dean (on behalf of the geomorph team: Dean, Mike, Antigoni, and Erica)
Dr. Dean C. Adams (he/him)
Distinguished Professor of Evolutionary Biology
string_agg | string_agg
+
2,1,3 | 3,2,1
(1 row)
so pre-sorting wouldn't be right (or at least it would change existing
behaviour in a surprising way).
Regards,
Dean
NaN or Inf. Testing that with
COPY with a few million numbers of different sizes, I observed a
10-15% performance increase.
So I'm feeling quite good about the end result -- I set out hoping not
to make performance noticeably worse, but ended up making it
significantly better.
Hi -
Is it possible for NiFi to automatically grant user access to NiFi based on an
OIDC authenticated users group membership matching a group in NiFi?
I'm using the latest 1.19.1 with OIDC enabled and integrated with Keycloak.
In Keycloak I have created a test user and assigned them to group
Rebased version attached.
Regards,
Dean
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
new file mode 100644
index b87ad5c..1482ede
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -396,8 +396,8 @@
originally matched appears later in the list of actions
On Mon, 2 Jan 2023 at 12:13, Dean Rasheed wrote:
>
> Re-reading my latest MERGE patch, I realised there is a trivial,
> pre-existing bug in the check for unreachable WHEN clauses, which
> means it won't spot an unreachable WHEN clause if it doesn't have an
> AND condition.
>
&g
Fix MERGE's test for unreachable WHEN clauses.
The former code would only detect an unreachable WHEN clause if it had
an AND condition. Fix, so that unreachable unconditional WHEN clauses
are also detected.
Back-patch to v15, where MERGE was added.
Discussion:
Fix MERGE's test for unreachable WHEN clauses.
The former code would only detect an unreachable WHEN clause if it had
an AND condition. Fix, so that unreachable unconditional WHEN clauses
are also detected.
Back-patch to v15, where MERGE was added.
Discussion:
ith target table attributes */
else if (TailMatches("MERGE", "INTO", MatchAny, "USING", MatchAny, "ON"))
COMPLETE_WITH_ATTR(prev4_wd);
else if (TailMatches("MERGE", "INTO", MatchAny, "AS", MatchAny,
"USING", MatchA
On Tue, 10 Jan 2023 at 08:33, Dean Rasheed wrote:
>
> The rest looks good to me, except there's a random non-ASCII character
> instead of a hyphen in "Kolmogorov-Smirnov" (because I copy-pasted the
> name from some random website).
>
Oh, never mind. I see you already fi
somewhat surprised that a case as simple as this wasn't covered by
any pre-existing regression tests.
Regards,
Dean
of a hyphen in "Kolmogorov-Smirnov" (because I copy-pasted the
name from some random website).
Regards,
Dean
om test to be run in parallel with others.
I didn't check the one-in-a-billion claim, but +1 for that.
Regards,
Dean
Try again. It just came up fine for me.
Cheers,
Muir
Sent from my iPad
> On Jan 9, 2023, at 9:08 AM, lynrbai...@supernet.com wrote:
>
> I have been shopping at vansciverbobbinlace.com or by snailmail since
about
> 1989. I check it almost every day. It is my go to shop. Imagine my
surprise
re standard-looking
RETURNING list, without a WITH clause.
Regards,
Dean
On Mon, 9 Jan 2023 at 15:26, Tom Lane wrote:
>
> Dean Rasheed writes:
> > So IMO all pseudorandom functions should share the same PRNG state and
> > seed-setting functions. That would mean they should all be in the same
> > (new) C file, so that the PRNG state can be k
gt; returning list expands to all the source columns, followed by all the
>> target columns.
>
> Does this lead to a problem in the event there are same-named columns between
> source and target?
>
Not really. It's exactly the same as doing "SELECT * FROM src JOIN tgt
ON ...". That may lead to duplicate column names in the result, but
that's not necessarily a problem.
Regards,
Dean
se to add a new "Random Functions"
section to the docs, and move the descriptions of random(),
random_normal() and setseed() there. That way, all the functions
affected by setseed() can be kept together on one page (future random
functions may not all be sensibly classified as "mathematic
icer
experience to allow the use of the raw json.
This adds a new buildartifact that was previously a static file
apidata.js and creates a new staticfile apidata.json which is what is
utilized to create apidata.js at build time (make/apidata.js).
Dean Galvin (1):
fix #4456: move apidata into sepe
ke a good point to stop playing around and get
feedback on whether this seems useful, or if anyone has other ideas.
Regards,
Dean
diff --git a/doc/src/sgml/ref/merge.sgml b/doc/src/sgml/ref/merge.sgml
new file mode 100644
index 0995fe0..4fc0a65
--- a/doc/src/sgml/ref/merge.sgml
+++ b/doc/src/sgml/ref/merge.
On Thu, 5 Jan 2023 at 13:21, Dean Rasheed wrote:
>
> On Thu, 5 Jan 2023 at 11:03, Alvaro Herrera wrote:
> >
> > > + /* Join type required */
> > > + if (left_join && right_join)
> > > + qry->mergeJoinType = JOIN_FULL;
>
On Sat, 7 Jan 2023 at 00:36, Nathan Bossart wrote:
>
> On Fri, Jan 06, 2023 at 06:52:33PM +, Dean Rasheed wrote:
> >
> > So I think we should use the same SQL clauses as every other psql
> > command that supports "S", namely:
>
psql: Add support for \dpS and \zS.
This allows an optional "S" modifier to be added to \dp and \z, to
have them include system objects in the list.
Note that this also changes the behaviour of a bare \dp or \z without
the "S" modifier to include temp objects in the list, and exclude
You are asking for the impossible. It is not possible to predict all
the possible ways a computer program could make a mistake. It's just
not knowable.
On 2023-01-06 17:22, Bite Gao wrote:
GnuCash Developers and Maintainers:
...
Personally, I do not found that how computer program
search_path.
So I think we should use the same SQL clauses as every other psql
command that supports "S", namely:
if (!showSystem && !pattern)
appendPQExpBufferStr(, " AND n.nspname <> 'pg_catalog'\n"
" AND n.nspname &
both create view and
> alter view.
>
Hmm, I don't think we should be offering "check_option" as a tab
completion for CREATE VIEW at all, since that would encourage users to
use non-SQL-standard syntax, rather than CREATE VIEW ... WITH
[CASCADED|LOCAL] CHECK OPTION.
Regards,
Dean
On Thu, 5 Jan 2023 at 12:52, Dean Rasheed wrote:
>
> While playing around with this, I noticed that the "... SET SCHEMA"
> case offers "FROM CURRENT" and "TO" as completions, which is
> incorrect. It should really offer to complete with a list of schem
Fix tab completion of ALTER FUNCTION/PROCEDURE/ROUTINE ... SET SCHEMA.
The ALTER DATABASE|FUNCTION|PROCEDURE|ROLE|ROUTINE|USER ... SET
case in psql tab completion failed to exclude = "SCHEMA", which
caused ALTER FUNCTION|PROCEDURE|ROUTINE ... SET SCHEMA to complete
with "FROM CURRENT" and "TO",
Fix tab completion of ALTER FUNCTION/PROCEDURE/ROUTINE ... SET SCHEMA.
The ALTER DATABASE|FUNCTION|PROCEDURE|ROLE|ROUTINE|USER ... SET
case in psql tab completion failed to exclude = "SCHEMA", which
caused ALTER FUNCTION|PROCEDURE|ROUTINE ... SET SCHEMA to complete
with "FROM CURRENT" and "TO",
Fix tab completion of ALTER FUNCTION/PROCEDURE/ROUTINE ... SET SCHEMA.
The ALTER DATABASE|FUNCTION|PROCEDURE|ROLE|ROUTINE|USER ... SET
case in psql tab completion failed to exclude = "SCHEMA", which
caused ALTER FUNCTION|PROCEDURE|ROUTINE ... SET SCHEMA to complete
with "FROM CURRENT" and "TO",
Fix tab completion of ALTER FUNCTION/PROCEDURE/ROUTINE ... SET SCHEMA.
The ALTER DATABASE|FUNCTION|PROCEDURE|ROLE|ROUTINE|USER ... SET
case in psql tab completion failed to exclude = "SCHEMA", which
caused ALTER FUNCTION|PROCEDURE|ROUTINE ... SET SCHEMA to complete
with "FROM CURRENT" and "TO",
Fix tab completion of ALTER FUNCTION/PROCEDURE/ROUTINE ... SET SCHEMA.
The ALTER DATABASE|FUNCTION|PROCEDURE|ROLE|ROUTINE|USER ... SET
case in psql tab completion failed to exclude = "SCHEMA", which
caused ALTER FUNCTION|PROCEDURE|ROUTINE ... SET SCHEMA to complete
with "FROM CURRENT" and "TO",
Fix tab completion of ALTER FUNCTION/PROCEDURE/ROUTINE ... SET SCHEMA.
The ALTER DATABASE|FUNCTION|PROCEDURE|ROLE|ROUTINE|USER ... SET
case in psql tab completion failed to exclude = "SCHEMA", which
caused ALTER FUNCTION|PROCEDURE|ROUTINE ... SET SCHEMA to complete
with "FROM CURRENT" and "TO",
601 - 700 of 57699 matches
Mail list logo
