-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add logs command to orientdb script #7130
Conversation
@eprothro thanks for the PR! I cannot merge it because you use the master branch we use only for releases. Could you create a PR against 2.2.x or develop branches? Thanks. |
@lvca done! (switched this PR to new base branch) |
Thanks, really appreciated. Any other ideas to improve the OrientDB experience? @santo-it could you please take care to document this? |
Thanks for asking! I'll share what would have helped me:
1. Have the library README be more focused at "get a user up and running" than "sell me on OrientDB".
2. Make creating/connecting to a database simplerI'm sure there are great reasons why connecting to a database is so coupled to the filesystem/network and/or particular options about storage, but they were neither intuitive to use, clear from the documentation, or easy to use. My top frustration was not being able to Also, noteworthy:
Once I got my own DB created, as I worked with it, anytime I restarted my console, connecting to the database again was inexplicably difficult, even using an absolute path to the exact directory. I eventually got it working, I couldn't tell you (or more importantly, one of my devs) how. Now, I could ignore this because, of course, I won't be using the console in dev, and programming a client will allow me to harden and hide however ugly this gets. But it is concerning to someone trying to evaluate OrientDB; this kind of issue can act as an indicator of things that lie further down the road. "If it's this clunky to create a database, what about when I get to complex operations?" 3. Better documentation for select/traverseMy getting started / quick POC path:
The learning curve was not too bad. Mostly, I was confused by the
|
Noted in the Release Notes @eprothro : hi, many thanks for your contribution and your feedback! |
My pleasure. Thanks for all the work on an exciting tool! |
As a first time user, I was searching for something like this, thought I would submit it in case y'all thought it had more broad usefulness.
my flow as a first time user: