I have just installed pgadmin 4.9 and am trying to edit several fields in my existing database. I right-click the table, select "View/Edit data" -> "All rows". Then in my table I change the data in a field of type "Text". When I then press the "Save" button, I get
'int' object has no attribute 'replace'
Changing the field via an "Update" script works fine though.
Has anyone else experienced this?
This is on Windows 10 and pgadmin runs in MS Edge.
This was a bug in pgAdmin4 when updating table and PK is of integer type.
It is fixed now and it will be available in next release, meanwhile you can use nightly build as a workaround.
Download: https://www.postgresql.org/ftp/pgadmin/pgadmin4/snapshots/2019-07-01/
---- UPDATE ----
pgAdmin 4 v4.10 is released with the fix.
Thanks to Murtuza for this answer.
I wrote an article (in french) about this problem, that I encountered with Laragon environment under Windows 10.
Hope it helps.
If you want it in English just ask me ;-)
See you
f-red
Related
I recently got a new laptop and downloaded pgAdmin 4 v3.0. Before now, I had been running pgAdmin 4 v2.0 with no issues. However, now whenever I try to open the Query Tool (just by going through the drop down Tools menu), I receive the error message "Query Tool Initialize Error". The Query Tool worked for two or three queries after the initial error message, but has been returning the error message whenever selected in the days since then. I am able to create and edit tables and views, but only by right clicking the icons on the left-hand side of the screen. I tried uninstalling and reinstalling pgAdmin to no effect.
Has anyone encountered this issue before?
Query Tool Initialize Error
In Ubuntu 16.04 I updated my pgAdmin 4 version 2.1 to 3.0 and saw the same thing when attempting to open the Query Tool through the drop down menus. While this is not a fix, instead of browsing to http://12.70.0.1:5050 I changed the URL to http://localhost:5050. Then I was able to use the Query Tool via the drop down menus.
Edit: What I did was edit the
pgAdmin4/lib/python3.5/site-packages/pgadmin4/config.py file by
updating the line:
DEFAULT_SERVER = '127.0.0.1'
to
DEFAULT_SERVER = 'localhost'
Now when I open pgAdmin, the Query Tool works accordingly.
Try resetting your layout, under the File entry in the top menu. I suspect that there's something in the layout settings saved under v2.0 that's incompatible with the v3.0 release.
I am using Netezza system where nps version is 7.2.0.6. I am trying to run a query on a view which is created on base table City_fact.
But getting above error.
Can someone please let me know in which scenario we get above error. I tried to find but was not successful.
I faced the same issue in Netezza after migrating from TWINFIN to MAKO version. Drop and recreating the view worked in my case. Not sure this will help . but a suggestion if any faced similar issue.
Regards,
Bharani Raj
This error was encounter when any base object id got changed (by alter table) which is used in any view, and that is not reflected in the view. in such case you need to refresh the view (Create or replace view)
To the best of my knowledge, I'm correctly importing my MS-SQL data source in the Control Panel (It says successful in green). I'm also pretty sure I'm importing the data correctly into the Windows 7 Publisher app since I can view the data in the DataView:
but when I go to the Layout View or Run Preview, I just get a blank chart:
It works if I use the default SimulatedTable but once I change the data source to my MS-SQL table, I can't get anything to display, no matter what display element I'm trying to use.
I've tried re-importing the data, using a different MS-SQL table, and re-naming the columns to match the SimulatedTable but it doesn't change the result. Can anyone tell me what I'm doing wrong?
Please try one thing, I am just guessing it might work.
Please select one of the Time Preset buttons and see if you see data in that(where there is blank) chart object.
If yes, then while setting up the time navigator object, select an option in drop down box labeled "Default Time Range Preset"
There are some hacks, please do let me know if run into some weirdness. It might not make sense if i try to explain unless you run into that situation.
Cheers,
I ended up giving up on the Windows 7 version of the application and running a virtual instance of Windows 8.1 instead so I could install the Datazen Publisher app for Windows 8.1. It's FAR less buggy.
Not perfect, though.
intellij idea data sources doesn't see existing table in my mysql database, while Netbeans see it.
i've created a table in the database. When i create connection in intellij idea data sources, it sees my scheme, i do select it in "schemas and tables" but then i don't see it in the list.
every schema, but mine's. When i try to connect to it with netbeans or mysql workbench, it's just ok. same story with several databases, with root access, too. any table, but mine's.
what could be wrong?
i see question like mine's here, related to visual studio, no answer.
please, give a good clue
I had the same problem in IntelliJ IDEA 15.
I fixed it by right clicking the data source -> Properties -> Schemas -> Use legacy introspector.
I found the reason of problem for HSQLDB: There is IDEA bug (i have 11.0 version).
Create db with relative path (relative of MODULE), like this:
jdbc:hsqldb:file:db_file/testDBInMemory;shutdown=true;hsqldb.write_delay=false;
f:\TestModule\db_file\
When added it to Data Sources, IDEA recognizes this path as relative of $IDEA_HOME$/bin folder.
f:\Program Files\JetBrains\IntelliJ IDEA 11.0\bin\db_file\
So you have two different data bases. And when JPA updated first, Data Source doesn't see update in other.
WORKAROUND:
use absolute path in file db url.
For the latecomers still experiencing this, Intellij IDEA also has the following features which might help you as they have me:
'Force Refresh' (ctrl + shift + F5): "The Force Refresh action clears the data source information from cache and loads it again from scratch."
'Forget Cached Schema' which clears the schema cache. Does require you to set which schema you want shown again.
Right click your datasource -> Diagnostics -> 'Force Refresh' or 'Forget Cached Schema'
Source: https://www.jetbrains.com/help/idea/cannot-find-a-database-object-in-the-database-tree-view.html
The answer for me was buried in a comment, so I'm posting it here. The symptom for me was seeing an error like this:
Unable to resolve table 'thetablename'
And the table name was highlighted in red.
The following fixes are all ways to trigger IntelliJ to refresh data sources:
CTRL+ALT+Y to refresh the db stuff, or
CTRL+F5, or
Click the database vertical tab on the right, expand, right-click on each DB connection and select 'Refresh'
Kudos to #ice for answering this earlier in a comment. I'm basically just elaborating and making sure this shows up as an answer.
Either the autocomplete in SQL Server Management Studio 2008 is buggy, or I am. Either way, when I try to type this and hit the spacebar:
SELECT TOP
Autocomplete immediately changes it to this (Topics is a table in one of our databases, btw):
SELECT Topics
Is there a way to fix, or at least gracefully work around this?
Unfortunately, no. SSMS Intellisense is a 1.0 product, and is not as feature-rich as many third-party products. You can turn it off OR ignore the suggestion (with the ESC key).
I think all you can do is hit ESC when the intellisense pop-up appears which will cancel any change it makes, or just turn Intellisense off completely by going to Text Editor -> Transact-SQL -> Intellisense.
I know this has been answered already but if you are looking for a tool that is quite useful/helpful try SQL Prompt from Red Gate. I have used this tool for years and found it is a great replacement for the built-in intellisense with plenty of options to allow for the tool help you be more efficient...
Also, you can cheesily add one column empty tables for the most common keywords you have issues with. Then it autocompletes to the table name but context puts it into the right usage.
Going one further you can:
CREATE table [top ] (c bit)
with the space at the end so the auto-complete is perfect.
After you create the object you'll want to hit CTRL-SHFT-R to refresh your Intellisense.