I'm attempting to install pgadmin4 4.27-1.f33 using the pgdg-common
repository on Fedora 33.
I get the following error message
Error:
Problem: conflicting requests
- nothing provides pgadmin4-python3-flask-compress >= 1.4.0 needed by
pgadmin4-4.27-1.f33.x86_64
Any suggestions?
Thanks,
Cliffor
On 10/31/20 5:17 PM, Clifford Snow wrote:
I'm attempting to install pgadmin4 4.27-1.f33 using the pgdg-common
repository on Fedora 33.
I get the following error message
Error:
Problem: conflicting requests
- nothing provides pgadmin4-python3-flask-compress >= 1.4.0 needed by
pgadmin4-4.27
When trying to populate the locations table I get this error:
psql:locations.sql:2105: ERROR: syntax error at or near ";"
LINE 2105: ...E Airport Way',null,'Portland','OR','97218',null,null,null);
^
Line 2105 is the last lin
On 11/1/20 10:53 AM, Rich Shepard wrote:
When trying to populate the locations table I get this error:
psql:locations.sql:2105: ERROR: syntax error at or near ";"
LINE 2105: ...E Airport Way',null,'Portland','OR','97218',null,null,null);
On Sun, 1 Nov 2020, Adrian Klaver wrote:
I'm hoping that it is:
'Every line prior to this one is terminated with a comma'
not colon.
Adrian,
That's the case. The only colons are within strings.
Thanks,
Rich
On Sun, Nov 1, 2020 at 7:54 PM Rich Shepard wrote:
>
> When trying to populate the locations table I get this error:
> psql:locations.sql:2105: ERROR: syntax error at or near ";"
> LINE 2105: ...E Airport Way',null,'Portland','OR','97218',null,null,null);
>
On Sun, 1 Nov 2020, Rich Shepard wrote:
Every line prior to this one is terminated with a colon. All other syntax
errors have been corrected.
Er, that's comma, not colon. Need to recaffinate.
Rich
On Sun, 1 Nov 2020, Francisco Olarte wrote:
This is nearly impossible to diagnose without a chunk of the query (
i,e, the first lines and the last ones ).
Francisco,
$ psql -d bustrac -f locations.sql
It smells to missing parentheses. If you use some editor witch matches
them, try adding on
On 11/1/20 11:04 AM, Rich Shepard wrote:
On Sun, 1 Nov 2020, Francisco Olarte wrote:
This is nearly impossible to diagnose without a chunk of the query (
i,e, the first lines and the last ones ).
Francisco,
$ psql -d bustrac -f locations.sql
It smells to missing parentheses. If you use som
On Sun, Nov 1, 2020 at 11:54 AM Rich Shepard
wrote:
> When trying to populate the locations table I get this error:
> psql:locations.sql:2105: ERROR: syntax error at or near ";"
> LINE 2105: ...E Airport Way',null,'Portland','OR','97218',null,null,null);
>
On Sun, 1 Nov 2020, Adrian Klaver wrote:
Also need the beginning lines including the INSERT part.
insert into locations (org_nbr,loc_nbr,loc_name,loc_addr1,loc_addr2,loc_city,state_code,loc_postcode,loc_phone,loc_fax,comment) values
(1,1,'2nd Bridge Gravel Bar','16156 Hwy 101 S',null,'Brookin
Rich:
On Sun, Nov 1, 2020 at 8:04 PM Rich Shepard wrote:
>
> On Sun, 1 Nov 2020, Francisco Olarte wrote:
>
> > This is nearly impossible to diagnose without a chunk of the query (
> > i,e, the first lines and the last ones ).
> Francisco,
> $ psql -d bustrac -f locations.sql
This is NOT the fi
On Sun, 1 Nov 2020, David G. Johnston wrote:
You encountered and asked on this exact same issue Friday...the advice in
that "Multi-row insert: error at terminal row." all still applies.
David J.
Which is why I did this file chunk-by-chunk.
Re-doing this by portions I find psql reporting erro
On 2020-11-01 11:50:31 -0800, Rich Shepard wrote:
> On Sun, 1 Nov 2020, David G. Johnston wrote:
> > You encountered and asked on this exact same issue Friday...the advice in
> > that "Multi-row insert: error at terminal row." all still applies.
>
> Which is why I did this file chunk-by-chunk.
Yo
On Sun, 1 Nov 2020, Peter J. Holzer wrote:
Your chunk still seems to be 2105 lines long.
Peter,
I've started from the top and work in 50-100 line chunks. I'm finding psql
errors that it had not flagged the first time through. So I'm working slowly
and carfully and expect to find all my typos
On Thu, 15 Oct 2020 at 03:53, Andreas Kretschmer
wrote:
> it seems to me a bug. i have a partitioned table:
I've just pushed a fix [1] for this to master only (PG14+)
The problem was that we only added the required information to allow
the executor to perform run-time pruning to the Append/Merge
16 matches
Mail list logo
