mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 13:36:03 +03:00
[GH-ISSUE #282] Multi data source #247
Labels
No labels
area-configuration
area-ct-app
area-ct-rdp
area-ct-remoteapp
area-ct-ssh
area-ct-vnc
area-launcher
area-list
area-tags
area-teamwork
bug
chore
dependencies
general-build/ci
general-performance
general-refactor
general-security
general-supportive
general-ux
meta-documentation
meta-enhancement
meta-enhancement
meta-feature
meta-help-wanted
meta-unknown-error
priority-hi
priority-low
pull-request
question
resolution-duplicate
resolution-invalid
resolution-wontfix
stale
task-put-off
task-still-considering
task-working-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/1Remote#247
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @VShawn on GitHub (Aug 30, 2022).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/282
Originally assigned to: @VShawn on GitHub.
Sometime we need a personal session database + some shared session database for work teams.
Database statue detector work with ASYNC@VShawn commented on GitHub (Sep 8, 2022):
here comes the list view
@majkinetor commented on GitHub (Sep 13, 2022):
Have you consider something database agnostic? 1RM certainly doesn't require non ANSI SQL.
Using postgresql should be equally easy as mysql and far more sane.
@VShawn commented on GitHub (Sep 14, 2022):
Actually we are required to use MySQL in the develop, so I started with MySQL first, mssql postgresql would be letter.
I trying to use VARCHAR only in create tabel. It would work (to my understanding) with most of the db.
Not very sure, I'm not expert of Database.
@majkinetor commented on GitHub (Sep 14, 2022):
Yeah, varchar works everywhere but you are limiting yourself if you only use that.
You need check if it is ANSI SQL or use ORM like entity framework.
@VShawn commented on GitHub (Oct 22, 2022):
almost done, @majkinetor you can try this one since you mentioned in https://github.com/1Remote/PRemoteM/issues/76#issuecomment-1246395658
1Remote alpha.01.zip
@Wikiphil commented on GitHub (Dec 31, 2022):
Hi,
Is this version will be merged with the main?
I configured my MySQL server and now all my entries are working on it. Pretty easy to configure, I'll try to access from another computer at the same time.
Regards.
@VShawn commented on GitHub (Dec 31, 2022):
Yes, this version will next generation of PRemoteM. But it's not a good choose to use this version, it not stable now： AKA you might lost your data.
I suggest you get build pack from GitHub action artifacts: https://github.com/1Remote/PRemoteM/actions/runs/3806712068
The package I uploaded on Oct 22 is now obsolete.
@Wikiphil commented on GitHub (Dec 31, 2022):
Done! I’ve updated to the latest version.
Views/Filters in the main windows are betters.
I'll test the readonly.
Thanks.
@Joly0 commented on GitHub (Jan 3, 2023):
Hey, this feature looks really cool and might be quite useful. Though a useful addition would be the possibility to define, if usernames and password are saved in the mysql database or in the local sqlite database.
This would be very useful for teams which all share the same servers, but dont share the same login or other servers for which the login is the same for every user.
I might be wrong, but i dont see this is possible at the moment, as far as i can see, the login is saved in the mysql and used for everyone that uses the mysql database
@VShawn commented on GitHub (Jan 4, 2023):
@Joly0 You are right,
sharing servers' address onlyis not possible for the current data structure.And if you ask me, I suggest everyone save their own login in the local sqlite db in this case.
Anyhow... We need a user authority management if we are going to satisfy
teams which all share the same servers, but dont share the same login. This means server-side\ more complex logic control \ management ui \ bla bla bla... That's too much work for me, I won't do that...