You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a question in regard to the design decision making process.
It seems to me that the storage and retrieval of translation memory data is a rather simple and straight-forward process without the need to manage complex transactions and/or employ specialized data types. (Correct me if I am wrong.)
Why settle for PostgeSQL when the lightweight SQLite would suffice?
The text was updated successfully, but these errors were encountered:
This is a question in regard to the design decision making process.
It seems to me that the storage and retrieval of translation memory data is a rather simple and straight-forward process without the need to manage complex transactions and/or employ specialized data types. (Correct me if I am wrong.)
Why settle for PostgeSQL when the lightweight SQLite would suffice?
The text was updated successfully, but these errors were encountered: