riopoderoso
Respectfully,
Jorge Maldonado
are part of the authentication
feature included in ASP.NET Core.
With respect,
Jorge Maldonado
On Tue, Apr 26, 2022 at 6:36 PM Tom Lane wrote:
> [ please keep the list cc'd ]
>
> JORGE MALDONADO writes:
> > As for the answer by *Tom Lane*, I am not restoring the DB but only
&g
Yes, I get a warning when running psql as follows. I will search for help
in Google and PostgreSQL documentation. The warning suggests *seeing psql
reference page "Notes for Windows users"*. I will do that. I had not
noticed the warning. Thank you.
[image: image.png]
Regards,
Jorge Mal
guage.
I will very much appreciate your valuable comments.
Respectfully,
Jorge Maldonado
On Mon, May 2, 2022 at 1:18 PM Adrian Klaver
wrote:
> On 5/2/22 12:24, JORGE MALDONADO wrote:
> > Hi,
> >
> > After a lot of tests and reading about the issue with the "*exc
-p 5433 -U postgres -W -s --exclude-table
'*."AspNet"*' riopoderoso
Password:
C:\Program Files\PostgreSQL\14\bin>pg_dump -f c:/temp/respaldo.backup -n
riopoderoso -F p -h localhost -p 5433 -U postgres -W -s --exclude-table
'*."AspNet"'* riopoderoso
Password:
tried different combinations of single quotes and double quotes but
none worked.
This behavior of characters other than lowercase letters in table names is
present no matter if the database is originally created with UTF8 encoding.
The problem persists in such a case too.
Regards,
Jorge Maldonado
characters for all languages are available and keep
*Collation* and *Character type* as *Spanish_Mexico.1252*. I guess that
using *UTF8* as the encoding method will keep databases more general. I
think that using *WIN1252* for encoding is restrictive.
Does it make sense?
Regards,
Jorge Maldonado
googled on performance comparison but have not found very much
information.
Best regards,
Jorge Maldonado
