```
cat /etc/clickhouse-client/conf.d/propmt.xml
<config>
    <prompt_by_server_display_name>
	    <default>{database}@{host} :) </default>
    </prompt_by_server_display_name>
</config>


cat /etc/clickhouse-server/conf.d/default_database.xml
<?xml version="1.0"?>
<yandex>
    <default_database>dw</default_database>
</yandex>

$ clickhouse-client
ClickHouse client version 21.6.5.37 (official build).
Connecting to localhost:9000 as user default.
Connected to ClickHouse server version 21.6.5 revision 54448.

default@localhost :) select currentDatabase();

SELECT currentDatabase()

Query id: efd2952e-a0d5-4250-be3c-5c3a929d3256

┌─currentDatabase()─┐
│ dw                │
└───────────────────┘
```

now: `default@localhost :)`
expected: `dw@localhost :)`
{
    if (!block)
        return;
    proc= block.rows();
    /// Even if all blocks are empty, we still need to initialize the output stream to write empty resultset.
    initOutputFormat(block, parsed_query);
    /// The header block containing zero rows was used to initialize
    /// output_format, do not output it.
     data if we're fuzzing.
    if (block.rows() == 0 || (query_fuzzer_runs != 0 && processed_rows >= 100))
        return;
    /// If results are written INTO OUTFILE, we can avoid clearing progress to avoid flicker.
    if (need_render_progress && (stdout_is_a_tty || is_interactive) && (!select_into_file || select_into_file_and_stdout))
        progress_indication.clearProgressOutput();
    try
    {
        output_format->write(materializeBlock(block));
        written_first_block = true;
    }
    catch (const Exception &)
    {
        /// Catch client errors like NO_ROW_DELIMITER