# JuliaDB doesn't install

**URL:** <https://discourse.julialang.org/t/juliadb-doesnt-install/94808>\
**Category:** New to Julia\
**Tags:** package\
**Created:** [February 17, 2023, 8:23pm UTC](https://discourse.julialang.org/t/juliadb-doesnt-install/94808 "2023-02-17T20:23:59Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![vsoler](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vsoler/32/30667_2.png) [@vsoler](https://discourse.julialang.org/u/vsoler)\
**Post date:** [February 17, 2023, 8:24pm UTC](https://discourse.julialang.org/t/juliadb-doesnt-install/94808/1 "2023-02-17T20:24:00Z")

</div>

I am trying to install JuliaDB on my PC but I get an error.

The problem is that it detects the presence of the package PooledArrays, which is somehow incompatible.

I installed PooledArrays some time ago, but I removed it with the “rm” command of the package manager.

I have executed “gc” Garbage Collection in the Package Manager, with no results.

What can I do if I want to install JuliaDB to give it a try?

Thank you

(@v1.8) pkg\> add JuliaDB  
Resolving package versions…  
ERROR: Unsatisfiable requirements detected for package PooledArrays [2dfb63ee]:  
PooledArrays [2dfb63ee] log:  
├─possible versions are: 0.3.0-1.4.2 or uninstalled  
├─restricted by compatibility requirements with JuliaDB [a93385a2] to versions: 0.4.1-0.5.3  
│ └─JuliaDB [a93385a2] log:  
│ ├─possible versions are: 0.9.0-0.13.1 or uninstalled  
│ └─restricted to versions \* by an explicit requirement, leaving only versions 0.9.0-0.13.1  
├─restricted by compatibility requirements with CSV [336ed68f] to versions: 0.5.0-1.4.2, leaving only versions: 0.5.0-0.5.3  
│ └─CSV [336ed68f] log:  
│ ├─possible versions are: 0.3.0-0.10.9 or uninstalled  
│ ├─restricted to versions \* by an explicit requirement, leaving only versions 0.3.0-0.10.9  
│ └─restricted by compatibility requirements with ClipData [39db22c5] to versions: 0.8.0-0.10.9  
│ └─ClipData [39db22c5] log:  
│ ├─possible versions are: 0.1.0-0.2.2 or uninstalled  
│ └─restricted to versions \* by an explicit requirement, leaving only versions 0.1.0-0.2.2  
└─restricted by compatibility requirements with DataFrames [a93c6f00] to versions: 1.2.1-1.4.2 — no versions left  
└─DataFrames [a93c6f00] log:  
├─possible versions are: 0.11.7-1.5.0 or uninstalled  
├─restricted to versions \* by an explicit requirement, leaving only versions 0.11.7-1.5.0  
└─restricted by compatibility requirements with DataFrameMacros [75880514] to versions: 1.0.0-1.5.0  
└─DataFrameMacros [75880514] log:  
├─possible versions are: 0.1.0-0.4.0 or uninstalled  
└─restricted to versions \* by an explicit requirement, leaving only versions 0.1.0-0.4.0

(@v1.8) pkg\> st  
Status `C:\Users\USUARIO\.julia\environments\v1.8\Project.toml`  
⌃ [6348297c] AlphaVantage v0.2.2  
[c7932e45] AstroLib v0.4.2  
[6e4b80f9] BenchmarkTools v1.3.2  
[336ed68f] CSV v0.10.9  
[324d7699] CategoricalArrays v0.10.7  
[8be319e6] Chain v0.5.0  
[39db22c5] ClipData v0.2.2  
[861a8166] Combinatorics v1.0.2  
[75880514] DataFrameMacros v0.4.0  
[a93c6f00] DataFrames v1.5.0  
[1313f7d8] DataFramesMeta v0.13.0  
[864edb3b] DataStructures v0.18.13  
[31c24e10] Distributions v0.25.80  
[38e38edf] GLM v1.8.1  
[dc211083] Gnuplot v1.4.1  
[bd48cda9] GraphRecipes v0.5.12  
⌅ [cd3eb016] HTTP v0.9.17  
[7073ff75] IJulia v1.24.0  
[41ab1584] InvertedIndices v1.2.0  
[b964fa9f] LaTeXStrings v1.3.0  
[945b72a4] MarketData v0.13.12  
[4f8c86c6] MarketTechnicals v0.6.0  
[b98c9c47] Pipe v1.3.0  
[ccf2f8ad] PlotThemes v3.1.0  
[f0f68f2c] PlotlyJS v0.18.10  
[91a5bcdd] Plots v1.38.5  
⌃ [c3e4b0f8] Pluto v0.19.9  
[7f904dfe] PlutoUI v0.7.49  
[274fc56d] PythonPlot v1.0.0  
[1a8c2f83] Query v1.0.0  
[ce6b1742] RDatasets v0.7.7  
[3eaba693] StatsModels v0.6.33  
[f3b207a7] StatsPlots v0.15.4  
[09ab397b] StructArrays v0.6.14  
[bd369af6] Tables v1.10.0  
⌅ [9e3dc215] TimeSeries v0.21.0  
[9d95f2ec] TypedTables v1.4.1  
[770da0de] UpdateJulia v0.4.2  
[10745b16] Statistics  
Info Packages marked with ⌃ and ⌅ have new versions available, but those with ⌅ are restricted by compatibility constraints from upgrading. To see why use `status --outdated`

---

<div class="post-metadata">

**Author:** ![nilshg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nilshg/32/2283_2.png) [@nilshg](https://discourse.julialang.org/u/nilshg)\
**Post date:** [February 18, 2023, 6:29am UTC](https://discourse.julialang.org/t/juliadb-doesnt-install/94808/2 "2023-02-18T06:29:21Z")

</div>

You should not install everything into the global environment but work with project specific environments instead. If you dump all your packages into the default environment you’re guaranteed to hit compat problems at some point.

For JuliaDB specifically note that the package has not been developed in a long time, so it will restrict compat to its dependencies to fairly outdated versions. No reason not to give it a spin in a fresh environment but something to keep in mind if you want to rely on it going forward.

---

<div class="post-metadata">

**Author:** ![rocco\_sprmnt21](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rocco_sprmnt21/32/20127_2.png) [@rocco\_sprmnt21](https://discourse.julialang.org/u/rocco_sprmnt21)\
**Post date:** [February 19, 2023, 11:22am UTC](https://discourse.julialang.org/t/juliadb-doesnt-install/94808/3 "2023-02-19T11:22:46Z")

</div>

> [@nilshg](#):
>
> but work with project specific environments instead

Could you explain in detail (step by step) how to create a separate environment to test a package that has compatibility issues?

---

<div class="post-metadata">

**Author:** ![nilshg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nilshg/32/2283_2.png) [@nilshg](https://discourse.julialang.org/u/nilshg)\
**Post date:** [February 19, 2023, 3:52pm UTC](https://discourse.julialang.org/t/juliadb-doesnt-install/94808/4 "2023-02-19T15:52:41Z")

</div>

Testing stuff is pretty easy as Pkg has built in support for temporary environments (which will automatically be cleaned up by `gc` when it’s next run). You just go:

```julia
] activate --temp

```

to get into a temporary environment, then `add` packages there as usual.

---

<div class="post-metadata">

**Author:** ![rocco\_sprmnt21](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rocco_sprmnt21/32/20127_2.png) [@rocco\_sprmnt21](https://discourse.julialang.org/u/rocco_sprmnt21)\
**Post date:** [February 19, 2023, 5:13pm UTC](https://discourse.julialang.org/t/juliadb-doesnt-install/94808/5 "2023-02-19T17:13:11Z")

</div>

Can I use this environment for several sessions?

---

<div class="post-metadata">

**Author:** ![nilshg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nilshg/32/2283_2.png) [@nilshg](https://discourse.julialang.org/u/nilshg)\
**Post date:** [February 19, 2023, 6:01pm UTC](https://discourse.julialang.org/t/juliadb-doesnt-install/94808/6 "2023-02-19T18:01:16Z")

</div>

No, I think it will get garbage collected. If you want an environment to persist make a directory for it, ie

```julia
; mkdir newdir; cd newdir
] activate.

```

Then you can re-activate this in a new session

---

<div class="post-metadata">

**Author:** ![cjdoris](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cjdoris/32/213133_2.png) [@cjdoris](https://discourse.julialang.org/u/cjdoris)\
**Post date:** [February 19, 2023, 10:31pm UTC](https://discourse.julialang.org/t/juliadb-doesnt-install/94808/7 "2023-02-19T22:31:26Z")

</div>

Or

```julia
] activate --shared some_name

```

to create a named persistent environment.

---

<div class="post-metadata">

**Author:** ![rocco\_sprmnt21](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rocco_sprmnt21/32/20127_2.png) [@rocco\_sprmnt21](https://discourse.julialang.org/u/rocco_sprmnt21)\
**Post date:** [February 20, 2023, 7:47am UTC](https://discourse.julialang.org/t/juliadb-doesnt-install/94808/8 "2023-02-20T07:47:46Z")

</div>

```julia
; mkdir newdir; cd newdir
] activate.

```

I hope to ask useful questions to others too (lazy like me or who can’t find the info on the manuals).  
The mkdir command on the shell doesn’t work for me.

```julia
shell> mkdir new_env
ERROR: IOError: could not spawn `mkdir new_env`: no such file or directory (ENOENT)
Stacktrace:

```

instead the cd command works.

```julia
shell> cd ..
C:\Users\sprmn\.julia 1.8.3

julia> pwd()
"C:\\Users\\sprmn\\.julia 1.8.3"

# I have a windows 10 system and this is my working environment

shell> cd v1.8.3
C:\Users\sprmn\.julia 1.8.3\v1.8.3

```

if i use command `activate -- shared some_name` the new directory is created under `C:\Users\sprmn\.julia\environments\`

```julia
C:\Users\sprmn\.julia\environments\some_name

```

Is it incorrect or not recommended to use workspace environments, like mine, outside this folder?