I'm trying to some basic mock tests. I want to return my ApiResponse when Mockmvc call the API but it doesn't.

@RunWith(MockitoJUnitRunner.class)
public class AuthControllerTest {

    @Autowired
    private MockMvc mockMvc;

    @InjectMocks
    AuthController authController;

    @Mock
    private AuthService authService;

    @Before
    public void init() {
        mockMvc = MockMvcBuilders.standaloneSetup(authController).build();
    }

    @Test
    public void authenticateUserShouldReturnStatusOk() throws Exception {
        LoginRequest loginRequest = TestUtils.createLoginRequest();

        AuthResponse authResponse = new AuthResponse("token", loginRequest.getUsername(), HttpStatus.OK);

        when(authService.authenticateUser(loginRequest)).thenReturn(authResponse);

        mockMvc.perform(post("/api/auth/login")
                .contentType(APPLICATION_JSON)
                .content(TestUtils.convertObjectToJsonBytes(loginRequest)))
                .andExpect(status().isOk())
                .andDo(print());

        verify(authService, times(1)).authenticateUser(refEq(loginRequest));
    }

}

MockMvc print result:

MockHttpServletRequest:
      HTTP Method = POST
      Request URI = /api/auth/login
       Parameters = {}
          Headers = [Content-Type:"application/json", Content-Length:"49"]
             Body = <no character encoding set>
    Session Attrs = {}

MockHttpServletResponse:
           Status = 200
    Error message = null
          Headers = []
     Content type = null
             Body = 
    Forwarded URL = null
   Redirected URL = null
          Cookies = []

Process finished with exit code 0

Why isn't that ApiResponse called? I want mockmvc to return the answer I gave, but nothing changes.

Can you help me?

As per lot of articles/google it is very hard to understand or explain the exact difference between test plan & strategy. Recently have gone through one of the interview and seems my answer didn't convince to the interviewer. So if anyone can help me in answering this to understand the thin line between Test plan & strategy please. Thanks.

The easiest way to create a sample database is to login to the container:

~]$ docker exec -ti mydb2 bash -c "su - db2inst1"

Once inside the container:

[db2inst1@e88eefa89d92 ~]$ db2sampl 
Creating database "SAMPLE"...

Connecting to database "SAMPLE"...

Creating tables and data in schema "DB2INST1"...

Creating tables with XML columns and XML data in schema "DB2INST1"...
'db2sampl' processing complete.
[db2inst1@e88eefa89d92 ~]$ db2 list db directory
System Database Directory
Number of entries in the directory = 1
Database 1 entry:
Database alias                       = SAMPLE

Database name                        = SAMPLE

Local database directory             = /database/data

Database release level               = 15.00

Comment                              =

Directory entry type                 = Indirect

Catalog database partition number    = 0

Alternate server hostname            =

Alternate server port number         =

If you don't want to use the sample database provided via db2sampl, you can create a database as part of the start of the container via -e DBNAME=MYSAMPLE:

docker run -itd --name mydb2 --privileged=true -p 50000:50000 -e LICENSE=accept -e DB2INST1_PASSWORD=whatever  ibmcom/db2 -e DBNAME=MYSAMPLE

Now you can try to connect to that database from data studio, setup your tables and inserting data.

we are running a mongo 2.6.5, 5 member replica set on CentOS and are looking to upgrade to 4.3.3. We do not use sharding. The tricky part for us is that we operate a service and can't have scheduled maintenance windows of very big size, so our hope is to minimize downtime to a few 10s of seconds early some morning. Our hope is that we could upgrade the cluster by just adding a new node to the cluster - one that is running newer mongo - let it get all sync'd up, and then remove one of the nodes running 2.6, and repeating the process until all the nodes are up to date.

So rather than actually upgrading nodes, we'd really be doing a fresh install on each one - we don't have to run a node's copy of the data through any sort of upgrade process but instead will treat it like temporarily expanding the replica set's size with a new server. Our desire to do it this way is to minimize downtime but also to allow us to proceed slowly - we want to bring up a new node and just let the dust settle for awhile, run some tests, etc. before proceeding. There are different elements of risk no matter which way we go, but our preference is for a process that changes few things at a time even if the overall end-to-end time is longer (we like lots of incremental changes spread out over time).

But when I try to add 4.3.3 nodes to 2.6.5 cluster, I get the following error:

"stateStr" : "(not reachable/healthy)",

When I take a look at the logs, it says:

2022-06-01T19:13:26.080+0000 [rsHealthPoll] couldn't connect to node1:27017: couldn't connect to server node1:27017 failed, connection attempt failed 2022-06-01T19:13:26.137+0000 [rsHealthPoll] warning: Failed to connect to 10.x.x.x:27017, reason: errno:111 Connection refused

Can you please help me?

I will edit this answer to include new limitations as I find them.

1. No triggers - limiting your options for auditing
2. No ownership chaining - according to https://docs.microsoft.com/en-us/answers/questions/528220/ideasuggestion-is-it-possible-to-support-ownership.html from 2021 this is coming in the future
3. No cross-database queries - also apparently a future feature
4. No FOR XML/FOR JSON clauses
5. No geospatial data types such as geography and geometry
6. No support for these data types: hierarchyid, image, text, ntext, sql_variant,xml https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-data-types
7. No EXECUTE AS, including inside CREATE PROC
8. No support for cursors ( https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-develop-loops )
9. IDENTITY(1,1) will not increment by 1 as you would expect. Instead any unique integer may be assigned when records are inserted to the table.

Other references:

• https://docs.microsoft.com/en-us/azure/synapse-analytics/sql/overview-features goes into differences between Dedicated and Serverless pools in Synapse

You can get the details of the latest checkpoint, including the time, from the pg_control_checkpoint() function:

SELECT * FROM pg_control_checkpoint() \gx
─[ RECORD 1 ]────────┬─────────────────────────

checkpoint_lsn       │ B/AF0C2EB8

redo_lsn             │ B/AF0C2E80

redo_wal_file        │ 000000040000000B000000AF

timeline_id          │ 4

prev_timeline_id     │ 4

full_page_writes     │ t

next_xid             │ 0:16691338

next_oid             │ 559103

next_multixact_id    │ 16340004

next_multi_offset    │ 326571432

oldest_xid           │ 726

oldest_xid_dbid      │ 1

oldest_active_xid    │ 16691338

oldest_multi_xid     │ 1

oldest_multi_dbid    │ 1

oldest_commit_ts_xid │ 0

newest_commit_ts_xid │ 0

checkpoint_time      │ 2022-05-23 08:18:02+02

There's three ways I can think of that you can go about this, in order of preference:

1. You have your application run the appropriate SQL scripts to alter the corresponding tables to add the new fields to. Typically one uses a prefix or suffix (e.g. ud for user defined) as a quick way to identify what fields are custom. I'm not opposed to having a separate meta-data table about those custom columns too, as you mentioned. This is fairly common practice among enterprise level software such as ERP systems.

2. You pre-bake in a fixed number of unused columns for each data type in each customizable table. E.g. IntColumn1 through IntColumn10, DateTimeColumn1 through DateTimeColumn10, VarCharColumn1 through VarCharColumn10, etc. Then your application allows the end user to "add" a new field by having them select the data type and the application chooses the next unused column of that type to map their new field to. I would probably put all of these additional fields into separate tables called OriginalTableNameExtension or OriginalTableNameCustom just so I wouldn't have to look at them and can manage them separately from the main tables. I've also seen this solution in the wild used by enterprise software.

3. The https://en.m.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80%93value_model , which is a single generic table that stores data of all different types. Similar to your meta-data table, typically it would have columns such as TableName, FieldName, FieldType, FieldValue and would store 1 row per value per field per table, in your case, all the custom fields. This allows the ability for custom fields to be created on the fly without any schema changes to the database, and is really flexible from a developer perspective. But it's unfortunately an https://softwareengineering.stackexchange.com/q/93124 . This is because the architectural structure can affect performance and makes it harder to index appropriately. It also causes queries to be written in less than usual ways to recompile the data needed to fit a specific use case for display reasons, especially when you start getting into analytical queries against the data.

I have a table and index in a PostgreSQL 10.18 database:

CREATE TABLE some_table (
    expires_at timestamptz
);
CREATE INDEX ON some_table(expires_at);

Is there a way to write this query in a way to use the index on expires_at?

SELECT
    *
FROM some_table
WHERE 
    TIMEZONE('America/New_York', expires_at)::date
  < TIMEZONE('America/New_York', NOW())::date
LIMIT 5;

America/New_York is added as an example, this query is run by using different time zones.

I have postgres 14 running on Windows 2019 server and I am using pg_basebackup to take regular backups.

The same powershell script which was working last week suddenly started giving me below errors. No changes happened in the system except a host reboot.

For testing purposes, I tried giving full access to everyone to the both data directory/backup directory and still the same error.

PS G:\FULL_Backup> Start-Process -FilePath "C:\Program Files\PostgreSQL\14\bin\pg_basebackup.exe" -ArgumentList "-D G:\FULL_Backup\PG_Basebackup_2022-05-16_085816", "-Ft", "-z", "-R", "-U postgres", "-w" -Wait -NoNewWindow
pg_basebackup: error: could not initiate base backup: ERROR:  could not stat file or directory "./base/18119/43980": Permission denied
pg_basebackup: removing contents of data directory "G:\FULL_Backup\PG_Basebackup_2022-05-16_085816"

Thanks, Udhayan

I have a table on MySQL 5.7 with the following definition and indexes:

+-------------------------+---------------+------+-----+---------+----------------+
| Field                   | Type          | Null | Key | Default | Extra          |
+-------------------------+---------------+------+-----+---------+----------------+
| id                      | int(11)       | NO   | PRI | NULL    | auto_increment |
| col1                    | int(11)       | YES  | MUL | NULL    |                |
| created_at              | datetime      | YES  |     | NULL    |                |
| archive                 | int(11)       | YES  | MUL | 0       |                |
...
+-------------------------+---------------+------+-----+---------+----------------+
+-------------+------------+------------------------------------+--------------+----------------------+-----------+-------------+----------+--------+------+------------+---------+---------------+

| Table       | Non_unique | Key_name                           | Seq_in_index | Column_name          | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | Index_comment |

+-------------+------------+------------------------------------+--------------+----------------------+-----------+-------------+----------+--------+------+------------+---------+---------------+

| my_table    |          0 | PRIMARY                            |            1 | id                   | A         |     1086069 |     NULL | NULL   |      | BTREE      |         |               |

| my_table    |          1 | indx1                              |            1 | archive              | A         |           1 |     NULL | NULL   | YES  | BTREE      |         |               |

| my_table    |          1 | indx2                              |            1 | archive              | A         |           1 |     NULL | NULL   | YES  | BTREE      |         |               |

| my_table    |          1 | indx2                              |            2 | created_at           | A         |     1086069 |     NULL | NULL   | YES  | BTREE      |         |               |

+-------------+------------+------------------------------------+--------------+----------------------+-----------+-------------+----------+--------+------+------------+---------+---------------+

When I run EXPLAIN SELECT * FROM my_table r WHERE r.col1 IN(1,4,6,10) AND (archive = 0) ORDER BY r.created_at DESC LIMIT 0,1001 I get:

+----+-------------+-------+------------+------+----------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+---------+-------+--------+----------+-------------+
| id | select_type | table | partitions | type | possible_keys                                                                                                                                      | key                                | key_len | ref   | rows   | filtered | Extra       |
+----+-------------+-------+------------+------+----------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+---------+-------+--------+----------+-------------+
|  1 | SIMPLE      | r     | NULL       | ref  | ...                                                                                                                                                | indx2                              | 5       | const | 158522 |    50.96 | Using where |
+----+-------------+-------+------------+------+----------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+---------+-------+--------+----------+-------------+

When I run EXPLAIN SELECT * FROM my_table r USE INDEX(indx1) WHERE r.col1 IN(1,4,6,10) AND (archive = 0) ORDER BY r.created_at DESC LIMIT 0,1001 I get:

+----+-------------+-------+------------+------+-------------------------+-------------------------+---------+-------+--------+----------+----------------------------------------------------+
| id | select_type | table | partitions | type | possible_keys           | key                     | key_len | ref   | rows   | filtered | Extra                                              |
+----+-------------+-------+------------+------+-------------------------+-------------------------+---------+-------+--------+----------+----------------------------------------------------+
|  1 | SIMPLE      | r     | NULL       | ref  | ...                     | indx1                   | 5       | const | 158522 |    40.00 | Using index condition; Using where; Using filesort |
+----+-------------+-------+------------+------+-------------------------+-------------------------+---------+-------+--------+----------+----------------------------------------------------+

It seems that in the first case, when not using the index hint, the query planner is not using created_at in the index because of the DESC clause, which MySQL 5.7 doesn't support. But why is it that in the extra column I see Using where when using indx2 and Using index condition; Using where; Using filesort when using indx1? The query also runs twice as fast. Why is that?

Edit: Adding SHOW CREATE TABLE output.

CREATE TABLE `my_table` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `col1` int(11) DEFAULT NULL,
  `created_at` datetime DEFAULT NULL,
  ...
  `archive` int(11) DEFAULT '0',
  PRIMARY KEY (`id`),
  KEY `indx1` (`archive`),
  KEY `indx2` (`archive`,`created_at`)
) ENGINE=InnoDB AUTO_INCREMENT=2298216 DEFAULT CHARSET=utf8

That character (0xEFBFBD in UTF-8) really is Unicode 0xFFFD, the “replacement character” �.

So if that's not what you want, the problem must have occurred when you inserted the data into the database. PostgreSQL does not surreptitiously modify strings, so some software most have done that before the data were put into the database.

Since the characters you would like to see are not all equal (I spot é and ç, for example), there is no automatic way to repair the damage.

Have a need to run an O/S bash script from an Oracle 19.6 database.

Here is my test case on my test database:

I want it to write out to a file, but right now I can't even get the job to run.

SQL> host cat test.sh
source /home/oracle/.bashrc
/bin/echo "TEST SCRIPT!" > test_script.out
/bin/echo “Job ok!”;
SQL> host /home/oracle/sql/test.sh

“Job ok!”

Result

  STATUS     ADDITIONAL_INFO
---------- -----------------------------------------------------
FAILED     EXTERNAL_LOG_ID="job_293887_405260",
           ORA-27369: job of type EXECUTABLE failed with exit co
           de: No such file or directory

HOWEVER, I've given it the whole path and creds with the secret password

SQL> host ls /home/oracle/sql/test.sh
/home/oracle/sql/test.sh
program_type        => 'EXTERNAL_SCRIPT',

program_action      => '/home/oracle/sql/test.sh',

number_of_arguments => 0,

enabled             => TRUE,
dbms_credential.create_credential(

credential_name => 'ORACLE_CRED',

username        => 'oracle',
DBMS_SCHEDULER.SET_ATTRIBUTE (

name => 'TEST_EXECUTABLE',

attribute => 'credential_name',

value => 'ORACLE_CRED');

What am I missing?