• TimeSeries.TimeArray
• DataFrames.DataFrame

Timestamp arrays should be concatenable.

1. Check that names are aligned
2. append! two vectors
3. sort! the result

Last step may include some checkups: if vectors are not overlapping, there is no need to sort!

Add joins by timestamp field.

Investigate, whether it would be possible to implement join with more keys. It looks rather straightforward: you should skip combinations, when keys are wrong. Of course, with high number of collisions it can be rather slow.

But only way to made it faster is to sort on keys, or implement some sort of index, which will make whole structure rather heavy.

As described in https://discourse.julialang.org/t/ann-plans-for-removing-packages-that-do-not-yet-support-1-0-from-the-general-registry/ we are planning on removing packages that do not support 1.0 from the General registry. This package has been detected to not support 1.0 and is thus slated to be removed. The removal of packages from the registry will happen approximately a month after this issue is open.

To transition to the new Pkg system using Project.toml, see https://github.com/JuliaRegistries/Registrator.jl#transitioning-from-require-to-projecttoml.
To then tag a new version of the package, see https://github.com/JuliaRegistries/Registrator.jl#via-the-github-app.

If you believe this package has erroneously been detected as not supporting 1.0 or have any other questions, don't hesitate to discuss it here or in the thread linked at the top of this post.

At the Github page of Timestamps.jl we can read.

WARNING: versions 0.1.* are not following semver and may contain breaking changes. Use at your own risk.

But in point 4 of Semantic Versions Specification we read

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be
considered stable.

So in fact changing ANYTHING in version 0.1.* or even 0.. is with agreement of semver. In such situation, why you didn't write

WARNING: with accordance to semver versions 0.1.* (or 0..)may contain breaking changes. Use at your own risk.

or something like that?

It looks like something akin https://github.com/mcabbott/AxisKeys.jl can be used to provide fast column name lookup, for tuple/vector based timestamps.

It was failing prior but I hoped it was because it couldn't find the package as a result of it not being registered. All tests are passing locally.

Timestamp construction
     - fields are constructed
  Error   :: (line:-1) :: fields are constructed
    Timestamp(Date(2000,1,1),12).timestamp => Date(2000,1,1)
Timestamp not defined

This issue is used to trigger TagBot; feel free to unsubscribe.

If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Merging is actually trivial with a call to vcat(x,y) but this method should default to sort=true, which makes it more useful.