Problems importing an OO database into LO

users
#101

My copy gives me the same Check-Sum!!

So what can be causing the problem??

#102

Hi :slight_smile:
I almost hate to say it this late in the process but wouldn't a non-java back-end be better?  Java just seems to be a bit of a disaster these days, since Oracle took over.  Kexi uses Sqllite and there are surely other light back-ends that might be good to try?
Regards from
Tom :slight_smile:

#103

Copying the structure and data in one go, as offered by the import
wizard, never creates any auto-ID fields.

Would this be a sensible improvement to make?

Mark Stanton
One small step for mankind...

#104

Am 21.04.2012 18:58, Mark Stanton wrote:

Copying the structure and data in one go, as offered by the import
wizard, never creates any auto-ID fields.

Would this be a sensible improvement to make?

Mark Stanton
One small step for mankind...

Hello Mark,

Yes, it would be useful to have more import options that actually work when importing a pseudo-database (mostly spreadsheet lists) into a true database or into HSQLDB at least:
[X] Use first column as column name
[X] Create primary key [Name Box]
   [ ] Create primary key as auto-ID

And another exclusive option:
[o] Use existing column <list box> as auto-ID
[ ] Use existing column(s) <multi-select list box> as primary key

When importing from a true database into another true database, these options should be preset according to the situation in the source table but still modifyable. Sometimes you want to import with no constraints at all.

My above statement

... never creates any auto-ID fields.

is not entirely correct. At least a copy&paste between 2 HSQLDBs creates the integer PK as auto-ID. It creates an exact copy of the table. Some level of detection seems to be implemented already.
Copying from HSQLDB to H2 (a similar Java DB) does creates an integer PK but not as an auto-ID field.

I think it can be very hard to implement for all types of connectable database engines. There are UNO interfaces to detect the capabilities and idiosyncrasies of some database driver. May be this can be utilized, may be not.

#105

to Andreas Säger <villeroy@t-online.de>

Hallo Andreas,

thank you for your short practical guide how to use a .dbf for serial letters.
I spent a lot of time fiddling around reading books etc. and couldnt come up
with a result. With your advice LO did what I want within some minutes. I
never understood what .odb is for: Its a simple container for a table etc.

so long

Walther

#106

I'm a little despondent - over a week since I started this exercise and I'm still nowhere. Also 3 days since my last post and no suggestions.

Can anyone help me out??

I stand at the point of having HSQLDB2.2.8 on my computer but when I try to create a new DB I get a "cannot load driver error" (see previous posts). Is it that you CAN'T CREATE a new Database this way?? )I can't believe this). Or what am I doing wrong??

I _HAVE_ to crack this urgently and need some more help from some of you experts out there.

What I need to do - Set-up HSQLDB2 (Done); Link to it (fail); Create a new table layout (pending); import my data via .csv (pending). START WORK AGAIN (urgent)!!!

Thanks a lot.

#107

What is the name of your database?
Answer:

     What folder are you going to use to hold the data?
Answer:

     What is the path to this folder?

Answer:

     Do you have the problems corrected the data in the database
already?

Answer:

     Is is this still the path to hsqldb?
Tools >Options > LibreOffice > Java > Class Path

Answer:

     With this information, I think someone will be able to help you
since these are the things you need to know to use hsqldb 2.2.8 as the
backend and Base as the front end.

--Dan

#108

Walther Koehler wrote

to Andreas Säger &lt;villeroy@&gt;

Hallo Andreas,

thank you for your short practical guide how to use a .dbf for serial
letters.
I spent a lot of time fiddling around reading books etc. and couldnt come
up
with a result. With your advice LO did what I want within some minutes. I
never understood what .odb is for: Its a simple container for a table etc.

so long

Walther

Walter, I think you refer to another topic:
http://nabble.documentfoundation.org/database-td3926217i20.html#a3928210
This mail belongs to thread "Problems importing an OO database into LO by
ptoye "

I'm sorry to disagree. Except for the "embedded HSQLDB" type of database,
Bases files do not contain any tables.
You always _connect_ some Base file to some database, spreadsheet, csv file,
to the address book of some email application. Then you can see the tables
of the connected data source. The tables are in some other file or
directory. In case of dBase you connect a Base document to a directory of
.dbf files. When you edit the data in the Base document or in Writer's data
source window, the connected .dbf file(s) will be modified, the Base
document remains untouched.
Normally you create the data source with some other software and connect a
Base document to it in order to user these data in office documents. The
status bar indicates the type and the location of the connected data source.
When Base creates a new database with new tables from scratch, the .odb file
carries the data source in the .odb. The status bar shows "embedded HSQLDB".
This topic deals with this embedded HSQLDB, why it should not be used
(except for demos and learning stuff), how to get such a database out of the
.odb so it can be used as an external database with better database
software, why Base never reached the status of a mature database
application, why it is extremely useful anyway, how to use Base in in other
ways than documented ...