[
https://issues.apache.org/jira/browse/TINKERPOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855026#comment-16855026
]
stephen mallette commented on TINKERPOP-1935:
-
I won't bother to re-open
Releases are announced and all branches are now re-opened. Please rebase
PRs as needed.
On Fri, May 31, 2019 at 2:22 PM Stephen Mallette
wrote:
> 3.3.7 VOTE just closed successfully and 3.4.2 looks like it will close the
> same way later this afternoon. We should be able to announce things
> off
Hello,
Apache TinkerPop 3.3.7 has just been released. It is mostly a maintenance
release along the 3.3.x line but it does come with a couple of features
worth noting. First, Gremlin Javascript now has an official way to support
DSL development and second, the Gremlin Console should better respect
Hello,
Apache TinkerPop 3.4.2 has just been released. It is mostly a maintenance
release fixing a number of bugs, but also introduces some new
functionality. In addition to some user facing features added in 3.3.7 (see
the upgrade notes for that version for more information), it also includes
an i
I think having a null literal makes sense. It plays well with existent SQL
providers, where there are representations for null:
https://docs.microsoft.com/en-us/dotnet/api/system.dbnull.value
I would propose another literal: UNSET. On some db providers, there's a
distinction between NULL, that cau
Hello Stephen,
Sounds like a great idea!
One more use case, returning `null` object in case property does not exist:
g.V().limit(1).coalesce(values('notSureIfExists'), constant(Null.instance()))
This would be very useful when working with steps that may fail on not existing
value. For example
