Reconciliation

Colin Law clanlaw at gmail.com
Mon Feb 23 11:55:10 EST 2015


Forwarding to the list for reference.

Colin

On 23 February 2015 at 16:53, Andy Pastuszak <apastuszak at gmail.com> wrote:
> Then XML is it for now.
>
> I understood the difference between sqlite3 and mysql.  I run a MySQL server
> in my house already, so it was a good place to consolidate everything.  But,
> for now, I'll stick with XML, since that's what's preferred.
>
> Now time to export, import and clean up.
>
> On Mon, Feb 23, 2015 at 11:45 AM, Colin Law <clanlaw at gmail.com> wrote:
>>
>> On 23 February 2015 at 16:19, Andy Pastuszak <apastuszak at gmail.com> wrote:
>> > Thank you for the help.  Luckily I only have transactions back to Feb
>> > 1st.
>> > The question for me now is stick with sqlite3 backend or switch to XML?
>> > I
>> > use GNUcash on 3 different computers in the house, so using the MySQL
>> > backend is appealing, since I don't need to deal with syncing my file
>> > across multiple PCs.  But, there is the question of backing up the data.
>> >
>> > Is ayone else using the sqlite3 data file format besides me?
>>
>> I think you are confused, sqlite and mysql are not the same.  If using
>> mysql then one can use a mysql server on one machine and access it
>> from several.  Using sqlite there is no server so this option is not
>> directly available.  You can still use file sharing to access the file
>> from multiple machines, but that is the same for xml or sqlite.
>> Whichever format you use you must make sure that access is limited to
>> one machine at a time, or data may be lost.
>>
>> Note also that the sql formats are not yet recommended for general use
>> as there may still be bugs in that area.
>>
>> Colin
>
>


More information about the gnucash-user mailing list