>-----Original Message-----
>From: Jim Callahan [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, December 5, 2007 12:11 PM
>To: [email protected]
>Subject: Re: [dba-dev] UNOized Copy Table Wizard: FLAT SOURCE
>
>> So I see no other option than executing a wizard dialog (and also a
>> table like control would help to show to the user the results of his/her
>> CSV configuration [field delimiter, etc]).
>>
>
>OpenOffice.org CALC has a CSV wizard that allows one to specify the field
>delimiter and preview the file. It works very well, but is limited to the
>65,000 some odd rows of a calc worksheet.
>

It has been a queston in my mind why that functionality was not included in 
Base, also. It seems the Base team tried to re-use as much of the existing code 
base as possible when the module was designed, why not that peice?

At this point, I suppose, that is a mute queston though.

>
>1. Pentaho (which provided JFreeReport Engine, has Kettle ETL module)
>
> - Pentaho Data Integration: Kettle is a powerful, metadata-driven ETL
> tool: http://kettle.pentaho.org/
>
>
>2. Talend
>
> - By delivering a full featured data integration platform leveraging
> Open Source, Talend makes data integration available to all types of
> organizations: http://www.talend.com/
>
>
>
>3. KETL
>
> - In 2005, in conjunction with Greenplum and JasperSoft, Kinetic
> Networks released the industry's first complete open source business
> intelligence development stack. The integrated solution combined KETL
> from Kinetic Networks, JasperReports, from JasperSoft, and the Bizgres data
> warehousing database based on PostgreSQL.:
> http://www.ketl.org/en/features/project_origins
>

I would add another name to those. http://apatar.com/index.html
OpenSource, GPL, straight ETL and what looks like a realatively straight 
forward toolkit for building a Base connector.

What is going on now with CopyTableWizard does address one class of Use Case 
scenario, a connector for something like apatar would surely fill another and a 
simple extension to help create text tables in embedded Base databases would, 
imo, round out the mix of usage scenarios quite well.

Drew



Reply via email to