Re: DBDI Status
On Thu, Jul 16, 2009 at 01:49:02AM -0700, Darren Duncan wrote: > Tim Bunce wrote: >> On Wed, Jul 15, 2009 at 03:46:08PM +0100, Sentra Systems wrote: >>> Do you want these to be typecast to 'Any'? >> >> In the short term, yes. In the longer term we'll need to be more >> flexible. I envisage a 'type map' file that, for each Java type, >> specifies the corresponding Perl6 type (either builtin or in a module). >> Any types not in the file would generate a warning and map to Any. >> >> Feel free to add that in! I'd guess it would be straight-forward. > > On that note, I've been using what influence I have over the Perl 6 > language design in the last few years to try and improve its savvy for > relational database features and semantics. > > I currently believe, as also documented indirectly in my Muldis D language > spec, that every SQL data type of any consequence already has a direct Perl > 6 counterpart, but that in general Perl 6's version is better where different. While that's likely to be useful in general for perl6 later, it's probably not that useful for the current goals of DBDI. We just need to be able to map the Java types used in the JDBC API to perl6 types that have sufficiently similar semantics. Remember that one of the goals of DBDI is to provide a common database API for _all_ the languages targeting Parrot. So we should avoid getting 'too clever' at this level. The Perl 6 types will be useful to whatever software is layered over the (relatively low-level) DBDI code. That's where the mythical "DBI 2" comes in. Having said all that... I expect DBDI to grow into a superset of JDBC that includes concepts and methods that enable greater performance and functionality. One significant idea here is that the higher level could should be able to supply DBDI with a row object that DBDI will just 'set' the fields of when it fetches a row. That sounds dull but it's actually significant for two reasons: a) it enables much higher performance as the same row with the same column variables (PMCs) can be reused for each row (assuming the app doesn't want to save them). That saves a huge amount of memory allocation and freeing. (That's a big part of why the DBI is so fast.) b) the field variables can be 'smart'. So, for example, the column in the row object that corresponds to an INTERVAL type could be an instance of a Perl6 Instant. Or any other object that will 'do the right thing' when the DBDI stores the value into it. Tim.
Re: DBDI Status
Tim Bunce wrote:
On Wed, Jul 15, 2009 at 03:46:08PM +0100, Sentra Systems wrote:
Do you want these to be typecast to 'Any'?
In the short term, yes. In the longer term we'll need to be more
flexible. I envisage a 'type map' file that, for each Java type,
specifies the corresponding Perl6 type (either builtin or in a module).
Any types not in the file would generate a warning and map to Any.
Feel free to add that in! I'd guess it would be straight-forward.
On that note, I've been using what influence I have over the Perl 6 language
design in the last few years to try and improve its savvy for relational
database features and semantics.
I currently believe, as also documented indirectly in my Muldis D language spec,
that every SQL data type of any consequence already has a direct Perl 6
counterpart, but that in general Perl 6's version is better where different.
For examples:
Perl 6 | SQL
-+-
undef| NULL
Bool | BOOLEAN, INTEGER(1), NUMBER(1), ...
Int | SMALLINT, MEDIUMINT, INTEGER, BIGINT, ...
Rat | NUMERIC, DECIMAL, ...
Num | FLOAT, DOUBLE, ...
Blob | BLOB, BINARY, VARBINARY, BIT, BYTEA, RAW, ...
Str | CHAR, VARCHAR, TEXT, CLOB, NATIONAL, VARCHAR2, LONG, ...
Instant | TIMESTAMP, ...
Duration | INTERVAL, ...
| DATETIME, DATE, TIME, ...
Now, spatial types aren't in the Perl core of course, but I'm sure that direct
analogies to GIS in SQL can be had reasonably in an extension.
And distinguishing various constrained versions of SQL types such as VARCHAR(10)
or what have you is just a "subtype Str10 of Str where { 0 <= $_.graphs <= 10 }"
or some such.
-- Darren Duncan
Re: DBDI Status
On Wed, Jul 15, 2009 at 03:46:08PM +0100, Sentra Systems wrote: > Tim > > They fixed a bug in rakudo last night that means a lot more of the pm's > build, still investigating the rest. There a number of additional classes > being discovered by javap (above the list you supplied). Yes, that list was just the top level classes. There's lots of extras that get referenced by those classes. > Do you want these to be typecast to 'Any'? In the short term, yes. In the longer term we'll need to be more flexible. I envisage a 'type map' file that, for each Java type, specifies the corresponding Perl6 type (either builtin or in a module). Any types not in the file would generate a warning and map to Any. Feel free to add that in! I'd guess it would be straight-forward. > Rakudo currently doesn't support 'Array of' - so the returns parameters are > now returning 'Array' without a type, I've included the type info in a > comment at the end of line. Method parameters just get the appropriate > sigil now. > > Typecasting was causing several multi methods to end up with the same > signature, I've amended the generator to remove the duplicates. Great. > I added them to a copy of the list and it starts bring in stuff like the > Java print system classes etc. when run against java2perl. Not quite sure what you mean there Dave. > Do you want a snapshot of what I've done so far, or would you rather wait > until it's more complete? Commit early, commit often :) > What sort of Google account do I need to commit? Go to google.com. Click 'Sign in' in the top righthand corner. Click 'Create an account now'. Enter your email address etc. Send me the email address when you're done. Or, if you already have a google account, just send me one of the email addresses associated with the account. Thanks! Tim.
Re: DBDI Status
Tim They fixed a bug in rakudo last night that means a lot more of the pm's build, still investigating the rest. There a number of additional classes being discovered by javap (above the list you supplied). Do you want these to be typecast to 'Any'? Rakudo currently doesn't support 'Array of' - so the returns parameters are now returning 'Array' without a type, I've included the type info in a comment at the end of line. Method parameters just get the appropriate sigil now. Typecasting was causing several multi methods to end up with the same signature, I've amended the generator to remove the duplicates. I added them to a copy of the list and it starts bring in stuff like the Java print system classes etc. when run against java2perl. Do you want a snapshot of what I've done so far, or would you rather wait until it's more complete? What sort of Google account do I need to commit? Dave
Re: DBDI Status
Many thanks Dave. Applied!
Tim.
On Fri, Jul 10, 2009 at 11:45:46PM +0100, Sentra Systems wrote:
> Tim
>
> Attached is a modified copy of the Generator::Std that emits current perl6.
> It's been amended to add the correct sigils and 'use' statements. Do you
> want to give it a try and see if it does what you want?
>
> :)
> Dave
>
>
> Tim Bunce wrote:
>> On Mon, Jul 06, 2009 at 02:08:17PM +0100, Sentra Systems wrote:
>>
>>> Tim
>>>
>>> Is there a particular reference implementation of java.sql(x) you're
>>> planning on running the java2perl on? A quick google shows a reference
>>> API but no obvious reference implementation.
>>>
>>
>> Any implementation that has the classes will do. java2perl6 is only
>> concerned with the class interfaces. It just runs javap on the class
>> you give it, parses the class and interfaces definitions it outputs, and
>> writes corresponding perl6 clasess and roles definitions.
>>
>> Try running
>>
>> java2perl6 --outdir jdbc --recurse --nest java.sql.Connection
>>
>> I've just checked in a file I had on my disk that lists all the
>> java.sql and javax.sql classess, so you can run
>>
>> java2perl6 --outdir jdbc --recurse --nest $(cat jdbc_classes.txt)
>>
>> Tim.
>>
>>
>>> Regards
>>> Dave
>>>
>>>
>>> Tim Bunce wrote:
>>>
On Sat, Jul 04, 2009 at 07:09:20PM +0100, Sentra Systems wrote:
> Hi
>
Hi Dave.
> Has anything happened with a Parrot JDBC implementation?
> Is Parrot stable enough yet?
> Has anyone mapped out the minimun subset of JDBC that would be required
> to get DBI working in Perl6?
>
Here's the (current) plan...
1. Dust off java2perl6
http://search.cpan.org/perldoc?java2perl6
http://code.google.com/p/java2perl6/
and update it to generate valid current perl6 code.
2. Add a type aliasing mechanism (ie "for the Java URL type use a Perl
Str type") to java2perl6 so we don't have to implement loads of Java
types before we can get started.
3. Write some kind of very dumb "Hello World" skeleton JDBC driver,
as a proof of concept that uses the interfaces generated by java2perl
4. Refactor Simon Cozens's SQLite3 DBDI driver to use ('consume') the
generated JDBC interfaces.
http://dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
That's not working right now, so here's a cached version:
http://google.com/search?q=cache:T8FN2WYvgm0J:dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
Making a move on this has been high on my list of pre-OSCON tasks
but working on NYTProf has remained a higher priority (there are some
great new features in the next release).
If anyone wants to help out with 1 and 2, you'd be more than welcome!
Send me your email address and I'll give you a commit bit.
Tim.
>>
>>
>
Re: DBDI Status
On Fri, Jul 10, 2009 at 11:45:46PM +0100, Sentra Systems wrote: > Tim > > Attached is a modified copy of the Generator::Std that emits current perl6. > It's been amended to add the correct sigils and 'use' statements. Do you > want to give it a try and see if it does what you want? Try running the mkjdbc.pl script (I've just updated). It now runs perl6 on the generated files to validate them. Lots of errors are generated, like the one below, but I'd guess there are only a few underlying problems. Any chance you could take a look? Tim. /Users/timbo/perl6/rakudo/perl6 jdbclib/java/sql/CallableStatement.pm Malformed method definition at line 11, near "read(\n" in Main (src/gen_setting.pm:3340)
Re: DBDI Status
Uh, I meant to add... give me an email address associated with a google
account and I'll give you a commit bit on http://code.google.com/p/java2perl6/
(I may move to github but it probably won't happen till after OSCON.)
Tim.
On Sat, Jul 11, 2009 at 01:03:25AM +0100, Tim Bunce wrote:
> Many thanks Dave. Applied!
>
> Tim.
>
> On Fri, Jul 10, 2009 at 11:45:46PM +0100, Sentra Systems wrote:
> > Tim
> >
> > Attached is a modified copy of the Generator::Std that emits current perl6.
> > It's been amended to add the correct sigils and 'use' statements. Do you
> > want to give it a try and see if it does what you want?
> >
> > :)
> > Dave
> >
> >
> > Tim Bunce wrote:
> >> On Mon, Jul 06, 2009 at 02:08:17PM +0100, Sentra Systems wrote:
> >>
> >>> Tim
> >>>
> >>> Is there a particular reference implementation of java.sql(x) you're
> >>> planning on running the java2perl on? A quick google shows a reference
> >>> API but no obvious reference implementation.
> >>>
> >>
> >> Any implementation that has the classes will do. java2perl6 is only
> >> concerned with the class interfaces. It just runs javap on the class
> >> you give it, parses the class and interfaces definitions it outputs, and
> >> writes corresponding perl6 clasess and roles definitions.
> >>
> >> Try running
> >>
> >> java2perl6 --outdir jdbc --recurse --nest java.sql.Connection
> >>
> >> I've just checked in a file I had on my disk that lists all the
> >> java.sql and javax.sql classess, so you can run
> >>
> >> java2perl6 --outdir jdbc --recurse --nest $(cat jdbc_classes.txt)
> >>
> >> Tim.
> >>
> >>
> >>> Regards
> >>> Dave
> >>>
> >>>
> >>> Tim Bunce wrote:
> >>>
> On Sat, Jul 04, 2009 at 07:09:20PM +0100, Sentra Systems wrote:
>
> > Hi
> >
> Hi Dave.
>
>
> > Has anything happened with a Parrot JDBC implementation?
> > Is Parrot stable enough yet?
> > Has anyone mapped out the minimun subset of JDBC that would be required
> > to get DBI working in Perl6?
> >
> Here's the (current) plan...
>
> 1. Dust off java2perl6
> http://search.cpan.org/perldoc?java2perl6
> http://code.google.com/p/java2perl6/
> and update it to generate valid current perl6 code.
>
> 2. Add a type aliasing mechanism (ie "for the Java URL type use a Perl
> Str type") to java2perl6 so we don't have to implement loads of Java
> types before we can get started.
>
> 3. Write some kind of very dumb "Hello World" skeleton JDBC driver,
> as a proof of concept that uses the interfaces generated by java2perl
>
> 4. Refactor Simon Cozens's SQLite3 DBDI driver to use ('consume') the
> generated JDBC interfaces.
>
> http://dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
> That's not working right now, so here's a cached version:
>
> http://google.com/search?q=cache:T8FN2WYvgm0J:dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
>
> Making a move on this has been high on my list of pre-OSCON tasks
> but working on NYTProf has remained a higher priority (there are some
> great new features in the next release).
>
> If anyone wants to help out with 1 and 2, you'd be more than welcome!
> Send me your email address and I'll give you a commit bit.
>
> Tim.
>
>
> >>
> >>
> >
>
>
Re: DBDI Status
Tim Some of the generated .pm's are failing under perl6. Will investigate further in the morning. :) Dave Tim Bunce wrote: Uh, I meant to add... give me an email address associated with a google account and I'll give you a commit bit on http://code.google.com/p/java2perl6/ (I may move to github but it probably won't happen till after OSCON.) Tim. On Sat, Jul 11, 2009 at 01:03:25AM +0100, Tim Bunce wrote: Many thanks Dave. Applied! Tim.
Re: DBDI Status
Tim
Attached is a modified copy of the Generator::Std that emits current
perl6. It's been amended to add the correct sigils and 'use' statements.
Do you want to give it a try and see if it does what you want?
:)
Dave
Tim Bunce wrote:
On Mon, Jul 06, 2009 at 02:08:17PM +0100, Sentra Systems wrote:
Tim
Is there a particular reference implementation of java.sql(x) you're
planning on running the java2perl on? A quick google shows a reference API
but no obvious reference implementation.
Any implementation that has the classes will do. java2perl6 is only
concerned with the class interfaces. It just runs javap on the class
you give it, parses the class and interfaces definitions it outputs, and
writes corresponding perl6 clasess and roles definitions.
Try running
java2perl6 --outdir jdbc --recurse --nest java.sql.Connection
I've just checked in a file I had on my disk that lists all the
java.sql and javax.sql classess, so you can run
java2perl6 --outdir jdbc --recurse --nest $(cat jdbc_classes.txt)
Tim.
Regards
Dave
Tim Bunce wrote:
On Sat, Jul 04, 2009 at 07:09:20PM +0100, Sentra Systems wrote:
Hi
Hi Dave.
Has anything happened with a Parrot JDBC implementation?
Is Parrot stable enough yet?
Has anyone mapped out the minimun subset of JDBC that would be required
to get DBI working in Perl6?
Here's the (current) plan...
1. Dust off java2perl6
http://search.cpan.org/perldoc?java2perl6
http://code.google.com/p/java2perl6/
and update it to generate valid current perl6 code.
2. Add a type aliasing mechanism (ie "for the Java URL type use a Perl
Str type") to java2perl6 so we don't have to implement loads of Java
types before we can get started.
3. Write some kind of very dumb "Hello World" skeleton JDBC driver,
as a proof of concept that uses the interfaces generated by java2perl
4. Refactor Simon Cozens's SQLite3 DBDI driver to use ('consume') the
generated JDBC interfaces.
http://dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
That's not working right now, so here's a cached version:
http://google.com/search?q=cache:T8FN2WYvgm0J:dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
Making a move on this has been high on my list of pre-OSCON tasks
but working on NYTProf has remained a higher priority (there are some
great new features in the next release).
If anyone wants to help out with 1 and 2, you'd be more than welcome!
Send me your email address and I'll give you a commit bit.
Tim.
Std.pm
Description: Perl program
Re: DBDI Status
On Mon, Jul 06, 2009 at 02:08:17PM +0100, Sentra Systems wrote:
> Tim
>
> Is there a particular reference implementation of java.sql(x) you're
> planning on running the java2perl on? A quick google shows a reference API
> but no obvious reference implementation.
Any implementation that has the classes will do. java2perl6 is only
concerned with the class interfaces. It just runs javap on the class
you give it, parses the class and interfaces definitions it outputs, and
writes corresponding perl6 clasess and roles definitions.
Try running
java2perl6 --outdir jdbc --recurse --nest java.sql.Connection
I've just checked in a file I had on my disk that lists all the
java.sql and javax.sql classess, so you can run
java2perl6 --outdir jdbc --recurse --nest $(cat jdbc_classes.txt)
Tim.
> Regards
> Dave
>
>
> Tim Bunce wrote:
>> On Sat, Jul 04, 2009 at 07:09:20PM +0100, Sentra Systems wrote:
>>
>>> Hi
>>>
>>
>> Hi Dave.
>>
>>
>>> Has anything happened with a Parrot JDBC implementation?
>>> Is Parrot stable enough yet?
>>> Has anyone mapped out the minimun subset of JDBC that would be required
>>> to get DBI working in Perl6?
>>>
>>
>> Here's the (current) plan...
>>
>> 1. Dust off java2perl6
>> http://search.cpan.org/perldoc?java2perl6
>> http://code.google.com/p/java2perl6/
>> and update it to generate valid current perl6 code.
>>
>> 2. Add a type aliasing mechanism (ie "for the Java URL type use a Perl
>> Str type") to java2perl6 so we don't have to implement loads of Java
>> types before we can get started.
>>
>> 3. Write some kind of very dumb "Hello World" skeleton JDBC driver,
>> as a proof of concept that uses the interfaces generated by java2perl
>>
>> 4. Refactor Simon Cozens's SQLite3 DBDI driver to use ('consume') the
>> generated JDBC interfaces.
>>
>> http://dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
>> That's not working right now, so here's a cached version:
>>
>> http://google.com/search?q=cache:T8FN2WYvgm0J:dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
>>
>> Making a move on this has been high on my list of pre-OSCON tasks
>> but working on NYTProf has remained a higher priority (there are some
>> great new features in the next release).
>>
>> If anyone wants to help out with 1 and 2, you'd be more than welcome!
>> Send me your email address and I'll give you a commit bit.
>>
>> Tim.
>>
>>
>
Re: DBDI Status
Tim
Is there a particular reference implementation of java.sql(x) you're
planning on running the java2perl on? A quick google shows a reference
API but no obvious reference implementation.
Regards
Dave
Tim Bunce wrote:
On Sat, Jul 04, 2009 at 07:09:20PM +0100, Sentra Systems wrote:
Hi
Hi Dave.
Has anything happened with a Parrot JDBC implementation?
Is Parrot stable enough yet?
Has anyone mapped out the minimun subset of JDBC that would be required to
get DBI working in Perl6?
Here's the (current) plan...
1. Dust off java2perl6
http://search.cpan.org/perldoc?java2perl6
http://code.google.com/p/java2perl6/
and update it to generate valid current perl6 code.
2. Add a type aliasing mechanism (ie "for the Java URL type use a Perl
Str type") to java2perl6 so we don't have to implement loads of Java
types before we can get started.
3. Write some kind of very dumb "Hello World" skeleton JDBC driver,
as a proof of concept that uses the interfaces generated by java2perl
4. Refactor Simon Cozens's SQLite3 DBDI driver to use ('consume') the
generated JDBC interfaces.
http://dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
That's not working right now, so here's a cached version:
http://google.com/search?q=cache:T8FN2WYvgm0J:dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
Making a move on this has been high on my list of pre-OSCON tasks
but working on NYTProf has remained a higher priority (there are some
great new features in the next release).
If anyone wants to help out with 1 and 2, you'd be more than welcome!
Send me your email address and I'll give you a commit bit.
Tim.
Re: DBDI Status
On Sun, Jul 05, 2009 at 01:58:11PM -0700, Harry wrote:
>
> Hi all,
Hi Harry.
> Is the parrot DBDI being worked on again.
I certainly plan to, as outlined below. If not by OSCON then certainly
at and after it.
Want to help out?
Tim.
> Harry
> Join team plico.
> http://www.hjackson.org/cgi-bin/folding/index.pl
>
>
>
> - Original Message
> From: Tim Bunce
> To: Sentra Systems
> Cc: dbdi-dev@perl.org; Simon Cozens
> Sent: Saturday, July 4, 2009 11:36:32 PM
> Subject: Re: DBDI Status
>
> On Sat, Jul 04, 2009 at 07:09:20PM +0100, Sentra Systems wrote:
> > Hi
>
> Hi Dave.
>
> > Has anything happened with a Parrot JDBC implementation?
> > Is Parrot stable enough yet?
> > Has anyone mapped out the minimun subset of JDBC that would be required to
> > get DBI working in Perl6?
>
> Here's the (current) plan...
>
> 1. Dust off java2perl6
> http://search.cpan.org/perldoc?java2perl6
> http://code.google.com/p/java2perl6/
> and update it to generate valid current perl6 code.
>
> 2. Add a type aliasing mechanism (ie "for the Java URL type use a Perl
> Str type") to java2perl6 so we don't have to implement loads of Java
> types before we can get started.
>
> 3. Write some kind of very dumb "Hello World" skeleton JDBC driver,
> as a proof of concept that uses the interfaces generated by java2perl
>
> 4. Refactor Simon Cozens's SQLite3 DBDI driver to use ('consume') the
> generated JDBC interfaces.
> http://dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
> That's not working right now, so here's a cached version:
>
> http://google.com/search?q=cache:T8FN2WYvgm0J:dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
>
> Making a move on this has been high on my list of pre-OSCON tasks
> but working on NYTProf has remained a higher priority (there are some
> great new features in the next release).
>
> If anyone wants to help out with 1 and 2, you'd be more than welcome!
> Send me your email address and I'll give you a commit bit.
>
> Tim.
>
>
>
>
Re: DBDI Status
Hi all,
Is the parrot DBDI being worked on again.
Harry
Join team plico.
http://www.hjackson.org/cgi-bin/folding/index.pl
- Original Message
From: Tim Bunce
To: Sentra Systems
Cc: dbdi-dev@perl.org; Simon Cozens
Sent: Saturday, July 4, 2009 11:36:32 PM
Subject: Re: DBDI Status
On Sat, Jul 04, 2009 at 07:09:20PM +0100, Sentra Systems wrote:
> Hi
Hi Dave.
> Has anything happened with a Parrot JDBC implementation?
> Is Parrot stable enough yet?
> Has anyone mapped out the minimun subset of JDBC that would be required to
> get DBI working in Perl6?
Here's the (current) plan...
1. Dust off java2perl6
http://search.cpan.org/perldoc?java2perl6
http://code.google.com/p/java2perl6/
and update it to generate valid current perl6 code.
2. Add a type aliasing mechanism (ie "for the Java URL type use a Perl
Str type") to java2perl6 so we don't have to implement loads of Java
types before we can get started.
3. Write some kind of very dumb "Hello World" skeleton JDBC driver,
as a proof of concept that uses the interfaces generated by java2perl
4. Refactor Simon Cozens's SQLite3 DBDI driver to use ('consume') the
generated JDBC interfaces.
http://dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
That's not working right now, so here's a cached version:
http://google.com/search?q=cache:T8FN2WYvgm0J:dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
Making a move on this has been high on my list of pre-OSCON tasks
but working on NYTProf has remained a higher priority (there are some
great new features in the next release).
If anyone wants to help out with 1 and 2, you'd be more than welcome!
Send me your email address and I'll give you a commit bit.
Tim.
Re: DBDI Status
On Sat, Jul 04, 2009 at 07:09:20PM +0100, Sentra Systems wrote:
> Hi
Hi Dave.
> Has anything happened with a Parrot JDBC implementation?
> Is Parrot stable enough yet?
> Has anyone mapped out the minimun subset of JDBC that would be required to
> get DBI working in Perl6?
Here's the (current) plan...
1. Dust off java2perl6
http://search.cpan.org/perldoc?java2perl6
http://code.google.com/p/java2perl6/
and update it to generate valid current perl6 code.
2. Add a type aliasing mechanism (ie "for the Java URL type use a Perl
Str type") to java2perl6 so we don't have to implement loads of Java
types before we can get started.
3. Write some kind of very dumb "Hello World" skeleton JDBC driver,
as a proof of concept that uses the interfaces generated by java2perl
4. Refactor Simon Cozens's SQLite3 DBDI driver to use ('consume') the
generated JDBC interfaces.
http://dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
That's not working right now, so here's a cached version:
http://google.com/search?q=cache:T8FN2WYvgm0J:dev.simon-cozens.org/6pan/browser/trunk/DBDI/DBDI/Driver/SQLite3.pm
Making a move on this has been high on my list of pre-OSCON tasks
but working on NYTProf has remained a higher priority (there are some
great new features in the next release).
If anyone wants to help out with 1 and 2, you'd be more than welcome!
Send me your email address and I'll give you a commit bit.
Tim.
DBDI Status
Hi Has anything happened with a Parrot JDBC implementation? Is Parrot stable enough yet? Has anyone mapped out the minimun subset of JDBC that would be required to get DBI working in Perl6? :) Dave
