Closed 8zero7 closed 5 months ago
Some additional context: I downloaded pgAdmin4 (which is terrible) and scripted the same tables as a CREATE statement. None of the columns have the "GENERATED BY DEFAULT AS IDENTITY" designation. This is a SQLPro Studio UI issue.
UPDATE: I updated to the latest version and this issue still persists. I even downloaded SQLPro for PostgreSQL (not Stuido) and I see the same thing. Deleted the app and reinstalled, same thing shows. If I create a new database, with a new table with one text column (non-identity), when viewing the table it also shows "GENERATED BY DEFAULT AS IDENTITY".
UPDATE 2: I connected to the same server from a different machine and the tables appear normal so this is definitely related to this one install. I feel like configuration is being cached on my machine so my effort to uninstall the app probably was not complete.
My new machine:
My other machine:
I confirmed with a co-worker that this is present on her machine as well. My other machine that does not seem affected is on version 2023.56. Trying to alter a table on the affected machines shows the value and it cannot be removed.
https://github.com/hankinsoft/SQLPro/assets/49440346/b90ea2cf-2ee2-4c40-bbed-cf956d84b2a9
Sorry about that. I’ve actually fixed this issue in the website build but unfortunately I’m currently away. I’ll get the App Store build fixed up first thing next week.
Pleaae see https://github.com/hankinsoft/SQLPro/issues/976 for details on the website build.
Ok great. Glad I wasn't going crazy. Thanks for the update.
Jason Rosensweig President Eight Zero Seven LLC
On Mon, May 20, 2024 at 9:35 AM Kyle Hankinson @.***> wrote:
Sorry about that. I’ve actually fixed this issue in the website build but unfortunately I’m currently away. I’ll get the App Store build fixed up first thing next week.
Pleaae see #976 https://github.com/hankinsoft/SQLPro/issues/976 for details on the website build.
— Reply to this email directly, view it on GitHub https://github.com/hankinsoft/SQLPro/issues/979#issuecomment-2120476395, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALZGMWSRPRYSQQ52T3FV34TZDH3ZZAVCNFSM6AAAAABH6U3C3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGQ3TMMZZGU . You are receiving this because you authored the thread.Message ID: @.***>
Just wanted to note that SQLPro for Postgres 2024.30 has been submitted to Apple and is in review. Usually it takes less than 24 hours for an update to be approved, so it should be available by this time tomorrow.
Great thanks
Jason Rosensweig President Eight Zero Seven LLC
On Tue, May 28, 2024 at 2:36 PM Kyle Hankinson @.***> wrote:
Just wanted to note that SQLPro for Postgres 2024.30 has been submitted to Apple and is in review. Usually it takes less than 24 hours for an update to be approved, so it should be available by this time tomorrow.
— Reply to this email directly, view it on GitHub https://github.com/hankinsoft/SQLPro/issues/979#issuecomment-2135883875, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALZGMWQVC5YALGJPIMGOQKDZETFCXAVCNFSM6AAAAABH6U3C3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZVHA4DGOBXGU . You are receiving this because you authored the thread.Message ID: @.***>
The new version should now be available. If you get the chance, please give it a try and let me know if that sorts things out for you.
Still shows .21 in the App Store. I'll check again later.[image: image.png] Sincerely,
Jason Rosensweig Owner / President Eight Zero Seven LLC @.***
On Wed, May 29, 2024 at 12:33 PM Kyle Hankinson @.***> wrote:
The new version should now be available. If you get the chance, please give it a try and let me know if that sorts things out for you.
— Reply to this email directly, view it on GitHub https://github.com/hankinsoft/SQLPro/issues/979#issuecomment-2137827841, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALZGMWXIAWKSDUAUDRCEVPDZEX7M5AVCNFSM6AAAAABH6U3C3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZXHAZDOOBUGE . You are receiving this because you authored the thread.Message ID: @.***>
Are you seeing the update now? If not, when you get the chance, could you reboot your macOS device and see if the update shows as available after that? Or try uninstalling the app, then re-install from the App Store is another way to force the latest version.
Yeah it showed up the next day. Seems to work fine. Thanks for fixing it so quickly.
Sincerely,
Jason Rosensweig Owner / President Eight Zero Seven LLC @.***
On Fri, May 31, 2024 at 1:01 PM Kyle Hankinson @.***> wrote:
Are you seeing the update now? If not, when you get the chance, could you reboot your macOS device and see if the update shows as available after that? Or try uninstalling the app, then re-install from the App Store is another way to force the latest version.
— Reply to this email directly, view it on GitHub https://github.com/hankinsoft/SQLPro/issues/979#issuecomment-2142653298, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALZGMWS72QOIALZCMARWFLLZFCUHVAVCNFSM6AAAAABH6U3C3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBSGY2TGMRZHA . You are receiving this because you authored the thread.Message ID: @.***>
Awesome, glad to hear it. If you happen to get the chance, would you consider leaving a rating or review on the App Store? As an independent developer, they help me out a ton. There is even a quick way to leave one, by running the query 'rate;'. No worries if not.
Left you a 5-star review on the app store
Sincerely,
Jason Rosensweig Owner / President Eight Zero Seven LLC @.***
On Fri, May 31, 2024 at 5:09 PM Kyle Hankinson @.***> wrote:
Awesome, glad to hear it. If you happen to get the chance, would you consider leaving a rating or review on the App Store? As an independent developer, they help me out a ton. There is even a quick way to leave one, by running the query 'rate;'. No worries if not.
— Reply to this email directly, view it on GitHub https://github.com/hankinsoft/SQLPro/issues/979#issuecomment-2142980994, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALZGMWUF36ABKPW5NZALT23ZFDRJXAVCNFSM6AAAAABH6U3C3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBSHE4DAOJZGQ . You are receiving this because you authored the thread.Message ID: @.***>
Describe the bug For any PostgreSQL table in any database (even production instances), all columns show "GENERATED BY DEFAULT AS IDENTITY" regardless of data type. This only started happening recently. None of these columns should be marked that way. Scripting the table as a CREATE statement also includes this for each column which is obviously impossible. Even the default postgres database tables all have this.
To Reproduce Steps to reproduce the behavior:
Expected behavior "GENERATED BY DEFAULT AS IDENTITY" should only appear next to columns marked with that option.
Screenshots
Environment details (please complete the following information):
Additional context n/a