[kexi] [Bug 349706] missing import option "object"

[Albrecht Will]

https://bugs.kde.org/show_bug.cgi?id=349706

--- Comment #5 from Albrecht Will <albrecht.will at online.de> ---
Hi Jaroslaw,

my very first intention during the import was getting the right type for a 
datafield to incorporate pictures later by hand. It is very important because 
every change of a field-type deletes all datas.
(In my very short test-data-base inserting by hand was possible.)

(For the following sentence you must know, I have 0,5% knowlegde of SQL)
Would I take over the real database of more then 2000 rows, and I would do any 
mistake or wanted to extend or change the DB, I would love to have a tool to 
store datas without loss and manipulate them in the table-format (what program 
ever).

Now you remark uuencoding!
First I had to infom myself. Then I controlled the output of an cvs-exported 
picture-field. If you look at the appendix - it seems the txt needs only an 
order ...  If you could do this, it would be great.:-)

I think, storing  a l l  datas in a csv format (that you can read, print and 
store for 100 and more years) is also an advantage of Open Source. 2515 you 
can reconstruct the DB's content.

Albrecht

Am Montag, 29. Juni 2015, 21:43:09 schrieben Sie:
> https://bugs.kde.org/show_bug.cgi?id=349706
> 
> Jarosław Staniek <staniek at kde.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED                 |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
> 
> --- Comment #4 from Jarosław Staniek <staniek at kde.org> ---
> Do you want to import fields of 'Object' type, i.e. binaries, for example
> images when importing from CSV?
> If so we need some assumptions, e.g. it's best if the CSV was created by
> Kexi or if you assure the the object's data encoded in CSV is in expected
> format. CSV specifications (if there are any) do not say anything about
> storing binaries :)
> If we agree on how they are stored in CSV, then we're closer to a solution.
> For example https://en.wikipedia.org/wiki/Uuencoding can be used.

-- 
You are receiving this mail because:
You are the assignee for the bug.