Re: Topics DBI::DBD::SqlEngine & derived

"H.Merijn Brand" <[email protected]>
Newsgroups gmane.comp.lang.perl.modules.dbi.sybase.devel
Message-ID <[email protected]>
On Tue, 04 Dec 2012 18:52:06 +0100, Jens Rehsack <[email protected]>
wrote:

> Hi Merijn,

Reply to summarize progress

> we should talk about
> - how to modify DBI::DBD::SqlEngine::TableSource and
>    DBI::DBD::SqlEngine::DataSource to allow chaining
>    (eg. fetch via http/ssh & decompress)

Still open, planned for today

> - easy way to configure the table-/datasources

Still open, planned for today

> - making DBD::CSV ready for dev-release (to get ideas about
>    chop-blank errors)

Ready, thanks to intens coorporation on IRC. Waiting for a
SQL::Statement release. Then I'll release a new DBD::CSV
that depends on it

> - feature request:
>    * skip-lines + columns line is first/second line
>    * columns line is "commented"

No priority. I'll have to think about these

> - compatibility support for $dbh->{f_meta}

Open, planned for discussion on IRC today

> - RT#81516 (close connected to $dbh->{f_meta} stuff}

Two possible fixes were posted by Jens yesterday. We'd
really (yes, REALLY) appreciate feedback on that ASAP.

> It would be great if Sven could join the discussion
> for AnyData/DBD::AnyData work (to avoid doing incompatible
> stuff) and Tim as well as Martin to have more people with
> better knowledge about DBI::DBD::SqlEngine/DBD::File internals.
> 
> I would also agree parts of the discussion happens via Skype,
> TeamSpeak (I can provide a server) or any other voice chat,
> if necessary.

Not an option in my $work environment

-- 
H.Merijn Brand  http://tux.nl   Perl Monger  http://amsterdam.pm.org/
using perl5.00307 .. 5.17   porting perl5 on HP-UX, AIX, and openSUSE
http://mirrors.develooper.com/hpux/        http://www.test-smoke.org/
http://qa.perl.org   http://www.goldmark.org/jeff/stupid-disclaimers/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.