OK. 
Actually, For 1), 2), 3),  the config is all the same. 

I prepared an environment like #3419, there is just one table :
--------------------------------------

CREATETABLE public.t_encrypt (

pwd varchar(32) NULL,

"content"varchar(32) NULL

)

--------------------------------------



And the config-encrypt.yaml is almost the same as #3419:
———————————————————
schemaName: encrypt_db


dataSource:
  url: 
jdbc:postgresql://127.0.0.1:5432/ds_encrypt?serverTimezone=UTC&useSSL=false
  username: postgres
  password: 123456
  connectionTimeoutMilliseconds: 30000
  idleTimeoutMilliseconds: 60000
  maxLifetimeMilliseconds: 1800000
  maxPoolSize: 50


encryptRule:
  encryptors:
    encryptor_aes:
      type: aes
      props:
        aes.key.value: 123456abc
    encryptor_md5:
      type: md5
  tables:
    t_encrypt:
      columns:
        user_id:
          plainColumn: plainpwd
          cipherColumn: cipher_pwd
          encryptor: encryptor_aes
        order_id:
          cipherColumn: cipher_content
          encryptor: encryptor_md5
———————————————————
On 11/19/2019 13:33,Zhang Yonglun<[email protected]> wrote:
Hi,

For 1:
If you can reproduce this problem, can you reply with the table structure?
And I will reopen that issue.

For 2:
Can you provide more information? Like config and SQLs.

For 3:
Is data updated successfully? Please provide more information like config
and SQLs.

If you like, please open new issues on GitHub for 2 and 3.


Zhang Yonglun
Apache ShardingSphere


Jiang Raigor <[email protected]> 于2019年11月19日周二 上午10:51写道:

Hi, everyone,

I found some issues with Sharding-Proxy when using postgres and collected
as follows:

First, I prepared an environment like:

https://github.com/apache/incubator-shardingsphere/issues/3419,

my postgres version is 12.0, and use the latest Proxy source code.
(commit 962a9656 zhaojun <[email protected]> on 2019-11-17 at 17:18)


The issues are:

1) Cannot find JDBC type '2003' in PostgreSQL column type (Existing)

https://github.com/apache/incubator-shardingsphere/issues/3104


2) receiveErrorResponse for postgres client (new)

When use JDBC client to insert record with Proxy, whether use Statement or
PreparedStatement, the Proxy can insert successful,
but the JDBC client receives error response.

Error log of Statement:
org.postgresql.util.PSQLException:
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288)
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:430)
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:356)
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:303)
at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:289)
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:266)
at org.postgresql.jdbc.PgStatement.executeUpdate(PgStatement.java:246)


Error log of PreparedStatement:
org.postgresql.util.PSQLException:
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288)
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:430)
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:356)
at
org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:168)
at
org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:135)

3) when update a record, response of num is 0 (new)

When use JDBC client to update record with Proxy, it will success, but the
result num is 0;
Otherwise, if excute update SQL without Proxy, the result num is 1;

I don't know if these issues need to be dealt with together?

获取 Outlook for Android<https://aka.ms/ghei36>

Reply via email to