![]() when jumping between tables via a FK => Currently, we can navigate between tab by cmd + and cmd + number. => We will have a plugin for each driver (MySQL, PostgreSQL, MS SQL.) about server monitoring. Hi About user management: current, we are not focus on this (only fetch and show data from table user of database), we will redesign it after finishing re-implement SQL auto suggestion.Ģ. If we'd go for TablePlus, we'd need a few licenses (<10), we were just wondering whether you guys are planning to have multiple plans, like a small business plan for N seats For Date and DateTime columns I'd love to use NOW and/or NOW() as value and TablePlus will expand it to the current time (or rather do something like SELECT NOW() and use that as value).If you aren't a fan of these kind of dropdowns (I sure am) I'd also be fine with having some kind of auto-completion for the current filter textbox.In Querious you can easily filter the current table with a nice overview of the available columns, e.g.We're an agency and thus work with a larger amount of servers, each having their own DBs, sometimes having multiple connections opened at the same time, you don't want to accidentally delete some data in prod if you just wanted to test it on local, etc. I'd love to give each saved connection a different color to distinguish them more easily.One possible solution (for me) would be the aforementioned navigation buttons (back and forward) or dividing both views into different tabs/views, like Querious does it: Switching between the query editor and back to the data viewer is kinda strange from an UX perspective since the query editor overlaps the data viewer but you have to click on a table to go back to your data view.I know TablePlus is solving this via tabs, but a Back and Forward button to navigate between tables (or rather the last spot you were at) would be super nice and convenient (e.g.I'd love to see a server tab just like in Querious to inspect various RDBMS-specific configuration such as Slow Queries, Variables (Session, Global), etc.You can't configure permissions per table, at least I haven't found it. ![]() You can give each connection a different color so it's easier to distinguish if you're on local, staging, live/prod) (Please don't mind the interesting color choice. Here's TablePlus' compared to Querious' user management The user management is very basic for such a rich tool.A big convenience feature that is just missing or too good hidden I can't seem to find whether there's a dialogue to create new databases.This is my feedback so far after some 30mins+ playing around with it: The fan also works fine.Ĭould it be something wrong with USB drive-routines, since the mouse and keyboard seems to not work? The same thing happened when I tried to boot Windows 7, even when the WHEA hadn´t occur.I'm currently evaluating the free version of TablePlus against our current editor of choice, Querious, for usage with MySQL (and probably Postgres in the not so distant future). In BIOS (F2-mode) indicates that everything is fine and all voltage and temperatures are well within given ranges. As I said earlier the NUC worked fine the first two weeks before this happened. Just the fact I can do all this indicates to me that the CPU works pretty fine, but something seems wrong with the HW-interface. If I start Ubuntu in memory check mode I´m able to run both RAM and HDD tests. After a couple of seconds it also shuts down. It loads all the way but the mouse and keyboard doesn´t work. I have also tried to boot UBUNTU 15 from an USB memory. It comes to the point to select what to do before it chrashes. I have also tried to reboot everything from the Windows 10 DVD. To my knowledge it must be something that WHEA detects about the hardware. In MS-DOS, that works fine, I have done some memory tests without detecting anything odd. I have also during that process gone into MS-DOS mode. In the repair mode I have gone back to an earlier recovery point without any effect. After a couple of times Windows give me a choice to enter repair mode. After that the boot process starts all over again. As soon as I get to the point there to enter my Password it just say Windows10 have detected WHEA and will start again as soon as it has written the logfile (that can´t be accessed). When I Power up the NUC it passes BIOS and start to launch Windows10. Hi, My problem is that I don´t get any code.
0 Comments
Leave a Reply. |