Hello to all, we have found the solution to our accents problem, a
colleague of mine got the idea to use xlsx instead of xls and the
magic happened, thanks to all for your support
best regards
El mié, 13 dic 2023 a las 0:19, Adrian Klaver
() escribió:
>
> On 12/12/23 16:09, Igniris Valdivia Baez
On 12/13/23 06:42, Igniris Valdivia Baez wrote:
Hello,
How is saved to xls files? --- using pentaho there is a tool there to
output data in different formats in this case xls
Defined reviewed, on particular is the data changed? ---Yes, some
descriptions are changed
How is transferred from xls to
Igniris Valdivia Baez wrote:
> 3. After the revision the data is loaded to the destiny database and
> here is were I believe the issue is, because the data is reviewed in
> Windows and somehow Pentaho is not understanding correctly the
> interaction between both operating systems.
On
Hello,
How is saved to xls files? --- using pentaho there is a tool there to
output data in different formats in this case xls
Defined reviewed, on particular is the data changed? ---Yes, some
descriptions are changed
How is transferred from xls to to the database? --- Using pentaho
there is a
On 12/12/23 16:09, Igniris Valdivia Baez wrote:
Hello to all, to clarify the data is moving this way:
1. The data is extracted from a database in postgres using Pentaho(Kettle)
2. Here is there is a bifurcation some data is loaded into the destiny
database and behaves fine the other scenario
Hello to all, to clarify the data is moving this way:
1. The data is extracted from a database in postgres using Pentaho(Kettle)
2. Here is there is a bifurcation some data is loaded into the destiny
database and behaves fine the other scenario the data is saved in xls files
to be reviewed
3.
On 12/12/23 15:54, Igniris Valdivia Baez wrote:
Please use Reply All to reply to list also
Ccing list
PgAdmin 4 but it looks the same in the console and from postman.
I believe that the problem is the xls that is generated from a postgres
database opened in Windows to fulfill a review
On 12/11/23 10:54, Igniris Valdivia Baez wrote:
hello to all, thanks for your answers i've changed the encoding using this:
ALTER DATABASE testdb
SET client_encoding = WIN1252;
now when we try to select data from a table we get this error:
ERROR: character with byte sequence 0xe2 0x80 0x8b in
On 12/12/23 12:44, Igniris Valdivia Baez wrote:
this is the result I got, now I have to figure it out how to solve it,
thank you so much
In what client are you viewing the data?
--
Adrian Klaver
adrian.kla...@aklaver.com
On Tue, 2023-12-12 at 15:44 -0500, Igniris Valdivia Baez wrote:
> this is the result I got, now I have to figure it out how to solve it,
Since you already have a replacement character in the database, the
software that stores the data in the database must be responsible.
PostgreSQL doesn't
this is the result I got, now I have to figure it out how to solve it,
thank you so much
El mar, 12 dic 2023 a las 14:42, Daniel Verite
() escribió:
>
> Igniris Valdivia Baez wrote:
>
> > hello, thank you for answering, it's not a typo, in the attachments
> > you can see that this is
Igniris Valdivia Baez wrote:
> hello, thank you for answering, it's not a typo, in the attachments
> you can see that this is actually my collation, algo a pic of the
> problem for more clarification,
This character is meant to replace undisplayable characters:
From
On Mon, 2023-12-11 at 13:54 -0500, Igniris Valdivia Baez wrote:
> El sáb, 9 dic 2023 a las 1:01, Laurenz Albe ()
> escribió:
> >
> > On Fri, 2023-12-08 at 23:58 -0500, Igniris Valdivia Baez wrote:
> > > hello, I have an ETL process collecting data from a postgresql
> > > database and xls files
On 12/11/23 10:54 AM, Igniris Valdivia Baez wrote:
hello to all, thanks for your answers i've changed the encoding using this:
ALTER DATABASE testdb
SET client_encoding = WIN1252;
now when we try to select data from a table we get this error:
ERROR: character with byte sequence 0xe2 0x80
hello to all, thanks for your answers i've changed the encoding using this:
ALTER DATABASE testdb
SET client_encoding = WIN1252;
now when we try to select data from a table we get this error:
ERROR: character with byte sequence 0xe2 0x80 0x8b in encoding "UTF8"
has no equivalent in encoding
On 12/9/23 07:54, Igniris Valdivia Baez wrote:
this is the settings for my local db which I failed to say is also in
Postgres 14, the dev db is in Postgres 15.4 has UTF an en_US.utf8
collation, for the ETL process I'm using Pentaho Data Integration
tool, also known as kettle, thanks in advance
this is the settings for my local db which I failed to say is also in
Postgres 14, the dev db is in Postgres 15.4 has UTF an en_US.utf8
collation, for the ETL process I'm using Pentaho Data Integration
tool, also known as kettle, thanks in advance
El sáb, 9 dic 2023 a las 10:50, Adrian Klaver
()
On 12/9/23 07:41, Igniris Valdivia Baez wrote:
hello, thank you for answering, it's not a typo, in the attachments
you can see that this is actually my collation, algo a pic of the
problem for more clarification,
thank you all
You picture shows the database collation as Spanish_Cuba.1252 not
hello, thank you for answering, it's not a typo, in the attachments
you can see that this is actually my collation, algo a pic of the
problem for more clarification,
thank you all
best regards
El sáb, 9 dic 2023 a las 1:01, Laurenz Albe
() escribió:
>
> On Fri, 2023-12-08 at 23:58 -0500, Igniris
On Fri, 2023-12-08 at 23:58 -0500, Igniris Valdivia Baez wrote:
> hello, I have an ETL process collecting data from a postgresql
> database and xls files and inserting in a postgresql database that
> process occurs great in a local DB in postgres 14 with UTF8
> codification and Spanish_Cuba.1952
20 matches
Mail list logo
