Let me clarify what I need to do. I need the raw data to move to a new
relational database. I'm not planning on having them work directly on
spreadsheets. The data will go into Salesforce, but I don't know how to
get the raw SQL data into Salesforce with the changes I need to make to
it before the move without exporting it.
I may have confused the discussion but not explaining my exact needs,
but that's because I (wrongly) tend to think I can do almost everything,
and only ask for help for specific issues I think I'm facing. There may
well be other ways to do this, but I was focused on what I thought was
the only way.
So...what I need is to remove the data from the current database
(apparently what I have is the best we can get), manipulate it so that
certain fields meet the requirements of the new database, then move it
into the new database. The only way I am aware of to get the data into
the new (Salesforce) database is in CSV files. Field mapping is done
via the first "row" of data (I need the field names), and I also need to
figure out what fields contain what data for the mapping process.
My goal was to use Base as a tool to extract the data, or perhaps even
accomplish the manipulations I need to do in prep for the move to
Salesforce. I thought I might be able to open or link to the data file
I have through Base and export it. That's because I haven't really
understood how to use SQL. I then realized I'd probably first need to
open or host the SQL data through MySQL or another variant of that.
Trouble is, I don't know how to do that. Alex gave some specific
suggestions which I will try today.
Honestly, though, I don't understand what MySQL does. Does it "open"
the data file, interpret the commands in it, and then allow the user to
manipulate and/or display the data correctly (with the correct
relational links)? And is that the only - or best - way to access the
data with Base? Can I just use MySQL to generate CSV files (or some
other format that Calc can open) for each of the tables in the file? At
this point, I'm not yet sure I have MySQL running properly, because it
ain't like any packaged software I've used in the past (and it's been a
LONG time since I've done and command-line work - like since the mid to
late 1980s). Or maybe there's an option I haven't thought of to
manipulate and move the data into Salesforce.
At this point I'm all ears. If I need MySQL for this, can someone
either point out a forum where I could get help with it or offer to
coach me (off list if need be) through the process of opening the data
and extracting it or connecting to Base?
OK, thanks, and sorry for the tome.
On 1/16/14 5:41 AM, Tom Davies wrote:
Hmmm, actually i've only just realised that a 2nd grab from the
'proprietary' back-end data-tables might not be such a nightmare.
Just keep a copy of the current export as it is so that the new grab
can be compared against it. Any differences could then be added to
the data-tables held fairly locally. Hopefully it's unlikely that
different updates would happen to a single old field both here and
Anyway, i guess my main question is could Base be used as the
front-end for data tables (the back-end) that is online?
On 16 January 2014 10:32, Tom Davies <email@example.com> wrote:
Thanks :) I guess that is part of my question. The original back-end
of the database in this case is MySql/MariaDb. Base can normally use
MySql/MariaDb as it's own back-end so there would seem to be 2
different routes that might be worth considering;
1. Attach Base directly to the existing MySql/MariaDb that is hosted
on some web-site (or at least on an internet-facing server such as a
Cloud). I know the back-end can either be on a local machine or on a
local-area-network but could it work over the internet too?
2. Since the exported data is already laid out for MySql/MariaDb then
just install MySql or MariaDb locally (onto the same desktop machine
that is using Base) or onto a LAN file-share so that all machines can
use Base (or other front-ends) to access the data. This seems to be
the route Alex is suggesting except he goes further and suggests using
a fairly local machine that already has MySql installed and just
adding the exports as a new file on that machine.
Carl, the o.p., seems to be thinking about the 3rd route and walking
headlong into the type of troubles Jay just outlined. As i see it the
problem with the 2nd or 3rd routes is that exporting data gives static
data. As time goes on the original database gets updated with new
data. So maybe at some point a new export might need to be grabbed
and then somehow figure out a way to merge the updated data at this
end with the updated data from over there. New records/rows are
tricky enough but tracking changes in fields/columns in individual
ancient records would be a complete nightmare. If it's a case of a
single snapshot to rescue data from a sinking Cloud then none of that
is a worry and the single export routes are perfect
So it's really route 1 that i'm curious about and really in a yes/no
way rather than in any detail. Carl doesn't seem to be thinking along
those lines so this is a bit of a tangent that will probably crop up
again in a future thread and be more relevant then.
Dover, NH 03820
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
- Re: [libreoffice-users] Connection to SQL database (continued)
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy