Re: Prepared_Statement :(

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2018-11-27 10:58, eduardsapotski@gmail.com wrote:
> Dmitry, if I wanted to get a universal solution, I would never use Ada-language.

I doubt universal solutions, especially if not in Ada! (:-))

> Over year ago I wrote trading terminal on Java. Uses JDBC and can easily change db-driver.

Surely they cannot. RDBMS are way too different for this to work. Any 
"universal" solution must include a DB adapter to provide a reasonable 
application interface instead of the SQL mess (prepared or uncooked (:-)).

> And application can be easily transferred to any server.
> But what's the problem?
> Year ago, trading was conducted on ten currency pairs, today more hundred pairs!
> Java slows down and eats resources.
> Server is running at the limit.
> I am not so rich to buy Oracle SPARC M8.
> Ada significantly reduces server load.

Though Ada is far faster than Java it alone does not guarantee 
performance if the DB is the bottleneck.

Ada allows very efficient custom persistent storage implementations when 
RDBMS fails. Here is a small comparison SQLite vs B-trees in Ada:

http://ada-programming.blogspot.com/2014/09/ada-direct-io-b-tree-vs-sqlite.html

 > For this reason, I am not going to use anything other but PostgreSQL.
 > PostgreSQL very fast on insert operations. Even much faster than 
Oracle, other things being equal.

I cannot tell if PostgreSQL is better than Oracle or MySQL or whatever. 
One should really benchmark them for the specific case to know.

What I know is that the difference cannot be any dramatic. If one of 
them stops working all others probably will, and conversely. So if you 
have a real DB problem you possibly must say goodbye to all relational 
SQL-based DBs and look for a better custom algorithmic solution.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de