i am running Adminer 4.8.0 on 2 machines:
my live production server: running mySQL 5.7.28
my local development machine: running mySQL 8.0.23
on the live server everything looks fine. on my local machine all of the engine/collation/row counts are all either blank or have question marks. see attached images:
apologies to #Shadow and others if this was posted in the wrong place, but i did find a solution to this issue:
in the Adminer source, replace this:
$R["Engine"]==($Zf=="pgsql"?"table":"InnoDB")
with this:
$R["Engine"]==(isset($Zf)&&$Zf=="pgsql"?"table":"InnoDB")
details of the issue are here.
looking at the GitHub ChangeLog this appears to be fixed in the next release.
hope this helps others. thanks.
Related
first of all I'm really sorry for my english. I started to build a fusionauth application on my Windows PC a few days ago. For this project I used a MariaDB. Now I buyed a vServer and my plan is to run Fusionauth with the help of docker.
After installing everything and following this tutorial: https://fusionauth.io/docs/v1/tech/installation-guide/docker
I had to change the .env file. But here you can only set a Username and Password for POSTGRES...
Don't really know what to do, because MariaDB should work with Fusionauth.
POSTGRES_USER=postgres
POSTGRES_PASSWORD=postgres
Would be grateful for every help!
MariaDB is no longer fully compatible with MySQL. Therefore, FusionAuth does not officially support MariaDB due to the fact that we are using modern MySQL functions and SQL. However, if you manage to get MariaDB working, post your solution to our forums (https://fusionauth.io/community/forum/) to let the community know.
We recommend using PostgreSQL for FusionAuth if possible, but MySQL also works. If you are going to use MySQL, you'll need to modify the Docker Compose file to use the MySQL Docker container instead of PostgreSQL.
The MySQL Docker container is documented here: https://hub.docker.com/_/mysql
Once you have MySQL running, you'll configure FusionAuth to connect to it using the environment variables that are documented here: https://fusionauth.io/docs/v1/tech/reference/configuration
I have just downloaded postgres and set everything up as per installation guide. I can connect to the db on the command prompt without any errors. When I use the pgadmin application I get many errors when clicking into any databases(the standard and any new ones created)
I have screenshots below. Could someone point me in the right direction. I have completely uninstalled postgres several times and has not fixed the problem.
In case you cant access image:
10:03:06:Error:Error rel.relhasoid does not exist
10:05:05: Error: column "prosiagg" doe not exist
I get a few more errors along those lines.
Thanks in advance
I'd like to backup a db today through localhost:8069/web/database/manager
, but the button return nothing while clicking the button.
Terminal show no error there.
Also invalid for duplicate, delete, create database,restore database and set Master password except link of existed db.
see pic as below:
the problem emerged since I deployed odoo12.
I can directly backup through pgAdmin4.
but I still want to know what happened.
My version of pgsql is 9.6 for odoo10 and odoo11.
It worked smoothly before I deployed odoo12
I found it's a stupid question.
the reason is that I connect to wrong db_host:
my conf set db_host as 127.0.0.1 but connect to localhost.
keep this topic for who make same mistake
I try to backup my university project database. I followed the instruction, everything seems to be inputed:
1:
2:
3:
But the only pop-out I get is this one in right-bottom corner of PGAdmin 4:
From the Official site, there should be another pop-up message, similiard to this one:
But I don't get this one, nor I get the other one that is displayed where any error occurs.
I tried to directly use pg_dump.exe, but it prompts me for a password. I tried all my passwords - user password, server password which I use to connect to my database in PGAdmin 4, other passwords, but none of them seem to work.
I tried to find any information about this, but all articles about pg_dump.exe are about how to automatize password input. What is the cause of this backup silent failure, and which password does pg_dump.exe need?
I'll add any details if needed, I was trying to figure it out for 4 hours now...
I've tried with pgAdmin4 1.4 and still my backup file was empty so I moved back to pgAdmin3 and it worked like a charm.
Although pgAdmin3 is not maintained anymore I suggest you use it until pgAdmin4 is up to it but right now it is way too slow.
Can you upgrade your pgAdmin4 with version 1.2 and try again?
https://www.pgadmin.org/
I think they have fixed the issue in new release.
Clearing the items in the path: C:\Users\yourUser\AppData\Roaming\pgAdmin seems to do the trick. Tested on PGadmin 4.29.
Be aware that all the sessions and saved servers will be gone.
I have installed the DSP(Dreamfactory Service Platform) locally on my Mac Book Pro using Bitnani.
I have a PostGreSQL server running locally on my Macbook, which I want to connect to using the DSP.
I am successfully able to connect to my PostGreSQL server from other applications, which essentially means that there is no problem with the setup.
However, on trying to connect the same from DSP I get the error:- "Failed to launch service "sql": CDbConnection failed to open the DB connection."
My connection string is :- "pgsql:host=localhost;dbname=Pinu"
Also, the password has been correctly entered.
The port is default as 5432. Whether or not I enter the same in the connection string, the connection always fails.
Even though I am trying to add the service as Remote SQL DB, I know that it's actually on the same local host. Not sure if that is the issue.
I also tried entering - 127.0.0.1 in place of localhost, but still I see the same issue.
Any help in this regard would be highly appreciated!
After talking to you via email, it looks like the root issue here is that you haven't successfully upgraded your DSP to the latest version. We are releasing DreamFactory version 1.8 on Bitnami tomorrow, so you should upgrade to the latest version.
As far as your PostgreSQL issue let's explore some options:
1) Connection strings:
a) pgsql:host=localhost;dbname=Pinu
b)
pgsql:host=localhost:5432;dbname-Pinu
c)
pgsql:host=localhost;port=5432;dbname=Pinu
2) If these don't work, try substituting your localhost with
127.0.0.1 (as you've tried previously, but test this in all scenarios).
3)
pgsql:host=localhost;port=5432;dbname=series1;schema=schema_name_here
Typically, Option A should work without a problem.
Give these a try if you would, and if you need some help upgrading then reach out to me again via email.
--Thanks,
Mark