graph-database

Description

日期转换函数timpstamp插入和保存都是int64，后面是否会支持yyyy-MM-dd HH:mm:ss这种形式，同时支持内部日期函数转换，将int64转换成yyyy-MM-dd HH:mm:ss。对于int64，现在的解决措施只能是应用内转换和新建string字段展示正常的日期格式

In Chapter 5. Schema and Data Modeling first there is paragraph:

The default cardinality setting is SINGLE. Note, that property keys used on edges and properties have cardinality SINGLE. Attaching multiple values for a single key on an edge or property is not supported.

and then example:

mgmt = graph.openManagement()
follow = mgmt.makeEdgeLabel('follow').multiplicity(MULTI).make()

Append class to all HashCodeBuilders in Gaffer for the below issue to minimise hash collisions.

@Test
    void name() {
        Foo foo = new Foo();
        Bar bar = new Bar();

        assertFalse(foo.equals(bar));
        assertNotEquals(foo.hashCode(), bar.hashCode()); //fails
    }

    class Bar {
        int a = 3;

        @Override
        public int hashCode() {

See #1029

Feature description (Mandatory)

Please add the capability to specify the type of array instead of defaulting to string. i.e.
apoc.array.int()

How this feature can improve the project?

By default, it is created as a string. Some customers have asked for the ability to hint at the data type.

If you do object.association.distinct.other_association, the distinct goes away.

This is probably good for the simple implementation, but we could have a WITH DISTINCT automatically go in there on the second association

https://matklad.github.io//2021/09/04/fast-rust-builds.html has some excellent advice on faster rust builds. Some of this might be useful for speeding up IndraDB's CI runs.

Per discussion in #2743 this class is mis-named.

Also, rename LinkStreamValue to just plain LinkStream.