Jump to content

VLDG

Members
 View Profile  See their activity

  • Content Count

    6

  • Joined

  • Last visited

Posts posted by VLDG

  1. Posted

    May be this

     

    Multi-row RETURNING behaviour

    Client-side INSERT … SELECT, UPDATE, DELETE, MERGE and UPDATE OR INSERT queries containing the RETURNING clause may now return multiple records instead of raising error “multiple rows in singleton select” as it happened before.

    These queries are now described as isc_info_sql_stmt_select during preparation, while in previous versions they were described as isc_info_sql_stmt_exec_procedure.

    Singleton INSERT … VALUES statements, as well as positioned UPDATE and DELETE statements (i.e. the ones containing the WHERE CURRENT OF clause) preserve the existing behaviour, being described as isc_info_sql_stmt_exec_procedure. They also preserve the ability of being executed within a single protocol roundtrip to the server.

    However, all these queries, if used in PSQL and the RETURNING clause is applied, are still treated as singleton.

     

     https://firebirdsql.org/file/documentation/release_notes/html/en/5_0/rlsnotes50.html#rnfb50-compat-returning

  2. Posted

    You can also define a default transaction to your connection with options readonly to true.

     

    In this case you have to be sure all dataset use this default transaction.

     

    With Delphi 12 you can also use SecurityOptions https://docwiki.embarcadero.com/RADStudio/Athens/en/What%27s_New#FireDAC_and_Security

     

    But for your case Brian answer is probably the best option.

  5. Posted

    2 hours ago, Dany Marmur said:
    2 hours ago, Dany Marmur said:

    MySQL out of the box is a glorified filesystem. It's spread and popularity is due to LAMP amongst other things*.

    Oracle, PostgreSQL and Firebird all tote "industrial strength" ACID compliance.

    PostgreSQL is syndicated open source whilst the Firebird is managed by a foundation out of Australia.

    IMHO the choice between PostgreSQL and Firebird (at the point you are) is more about choosing the governance of the OS project.

     

    Personally, i went from Access and Paradox to Firebird 1.0. Never looked back. FB rocks!

     

    * MySQL, M$SQL and other "mass" market brands throw in a lot of "candy" and "chrome" into the server engine. That might be convenient for some developers but it degenerates the SQL whitepapers and may very well throw problems at you in the future (when you realize MySQL will not cut it). This is opinionated.

    I agree Firebird is a rock and "200,000 records per year in the main table" will be ok for any database !

     

×