discussed just after at OSCON.
In conclusion, I regret not being able to attend OSCON, but I wish
that any of you who are there will have a good time.
Thank you. -- Darren Duncan
P.S. I will be away from home July 13th-19th, so no uploads will
happen on those days; anything will happen before
? And
how many others are on older versions of 5? Or, heavens forbid, 4.x
or older? Where can I lookup such info, *other* than on Google?
-- Darren Duncan
by
default is like having the popular CGI module's param() return
received query parameter values by default without un-url-escaping
them.
-- Darren Duncan
keywords. Insensitive identifiers are equivalent to the same letters
uppercased when made case-sensitive, as I understand it.
Also, if SQL is generated rather than hand-written, the difference is trivial.
-- Darren Duncan
, which *may*
be in time for the DBI Users BoF.
Good day. -- Darren Duncan
for *everything* to be accessible by a method
call. Its a lot more consistent, and I believe it leads to cleaner
code, and as you say, it avoids some kinds of silent errors.
And of course, adding these methods doesn't have to break the old
interface, so no worries there.
-- Darren Duncan
At 7:56 PM -0400
was for interface uniformity, to take those last
few tied hold-outs and make method-form equivalents for them. This
sort of thing is not supposed to be the domain of a wrapper module.
-- Darren Duncan
P.S. This has nothing to do with the merits of SQL; that's a separate matter.
2004-08-06 Darren Duncan [EMAIL PROTECTED]
--
Finally, after 19 months of waiting, since the first notice of this
project was uploaded to CPAN (2003-01-05), I am pleased to announce
that the first developer release of my Rosetta database
that, might
break.
Any feedback? Can we do this thing? Or are there any good reasons not to?
-- Darren Duncan
maintained, and said maintainers will be able to respond quickly to
raised issues.
In order to keep from bloating this Roadmap thread, I will post my
first suggestion in a few moments under a different subject line.
-- Darren Duncan
to be rigorous under the circumstances.
-- Darren Duncan
() or finalize(), etc).
FYI, I see the main advantage of weakrefs being for people that
simply let their handles go out of scope rather than explicitly
destroying/closing them. Which is fine, since that is often seen as
the Perl way.
-- Darren Duncan
() or finalize(), etc).
FYI, I see the main advantage of weakrefs being for people that
simply let their handles go out of scope rather than explicitly
destroying/closing them. Which is fine, since that is often seen as
the Perl way.
-- Darren Duncan
could *also*
be static if the DBD is more limited and only connects to one type of
database, but that is optional since only some DBD can implement a
static version.
-- Darren Duncan
, but not really what I want.
Anyone familiar with MakeMaker that can help me with this? Namely,
what do I change in my Makefile.PL to achieve the desired effect?
Thank you. -- Darren Duncan
, if the only way to do DDL in a routine is with dynamic SQL,
then I would like to know.
Thank you in advance. -- Darren Duncan
Mac OS X 10.2.
Thank you again. -- Darren Duncan
At 10:48 AM +0100 9/19/04, Matt Sergeant wrote:
On 18 Sep 2004, at 22:00, Darren Duncan wrote:
This afternoon, the http://www.sqlite.org/ was updated to declare
that SQLite 3.x is now officially stable with the new 3.0.7
release; previously it was in beta status. This is a big milestone.
One
At 7:34 PM +0100 9/21/04, Matt Sergeant wrote:
I've updated to 3.0.7, but not done named params yet. 1.06 is
heading to CPAN as I type this. 1.07 will add the named params.
Sounds great, thanks. -- Darren Duncan
comprehensive testing
of my own code that uses it did not return any errors.
Perl 5.8.5, default config, on Darwin / Mac OS X 10.2.8, GCC 3.3,
with both DBD::SQLite 1.0.7 and DBD::mysql 2.9004 (drivers installed
first, against 1.43).
-- Darren Duncan
whether the
current $dbh will use actual or emulated prepared statements. Unless
one already exists.
Thank you. -- Darren Duncan
subscribed to dbi-dev, since it is very low
traffic, but I will stick to replies to other topic threads, such as
Tim's request to test the 1.46 release candidate, rather than
starting my own.
-- Darren Duncan
is a port of DBI to parrot. Either that, or perhaps a better solution
would be to have a number of sites popping up like foo.parrotcode.org to
cover Parrot specific projects. -- Darren Duncan
is that of encoding the individual parts of the
URI, in case, for example, the password contains a : or / etc, or if
there are differing case-sensitivity issues. Perhaps the format of
delimited SQL identifiers could provide an example to follow.
-- Darren Duncan
job or in response to a user's manual
query. In the latter case, the result would be more user friendly,
as what they see is what they can open (privileges not withstanding).
-- Darren Duncan
errors, and return
appropriately mapped ones that work? As I said, data_sources()
wouldn't be called too often so this speed hit should be acceptable;
it's better that the results actually are valid, I think. -- Darren
Duncan
At 2:13 PM + 12/15/04, Jeff Zucker wrote:
Darren Duncan wrote:
How much trouble would it be to actually look inside each file?
Lots of trouble. Since DBD::DBM supports many DBM types and many
MLDBM types, one file might be SDBM, another Berkeley_DB, etc. and
each of those might use MLDBM
a user does is create an environment handle object,
off of which they call connect(), which incidentally saves us having
to use any package globals. -- Darren Duncan
AnyData so SQL-Statement's test suite
could get past that, there is still a problem since it seems to
require DBD-Pg now, and several other drivers. SQL-Statement 1.11
didn't have these issues. All those dependencies seems inappropriate.
-- Darren Duncan
At 9:38 AM +0200 4/21/05, H.Merijn Brand
somewhat
like the 1.13 problems.
-- Darren Duncan
want, and you can run init() prior to forking without
trouble.
What I've said in this email is not exhaustive and I may add or amend
items later; but, its a good start. Feedback is welcome of course.
Thank you. -- Darren Duncan
driver names are quite short already, so its not
like abbreviations are necessary.
-- Darren Duncan
here, so do as you will.
-- Darren Duncan
be met by the actual DBMS that Perl + DBI needs to work with.
What you say is fair enough, but I never proposed anything impossible
or difficult; everything that I am proposing here is easy and simple.
-- Darren Duncan
.
-- Darren Duncan
At 1:22 AM -0700 7/9/05, Jonathan Leffler wrote:
On 7/4/05, Darren Duncan
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] wrote:
5. All details used to construct a connection handle should be
completely decomposed rather than shoved into an ungainly data
source. Examples of what should be distinct
many levels of hierarchy there can
be with a database; eg, a server has 1+ databases, each of which has
1+ catalogs (and presumably each of those has 1+ schemas and each of
those 1+ tables and other schema objects). I will probably find it
helpful when I plan various DBI-using tasks.
-- Darren
could not do with a traditional bind_param()
etc since the whole thing won't fit in RAM at once.
-- Darren Duncan
in reference
documentation?
-- Darren Duncan
,
because those specify a versioned API which continues to exist as a
wrapper. See http://arstechnica.com/reviews/os/macosx-10.4.ars/4 for
what I'm talking about.
However it's done, I'm thinking something akin to that would be good for DBI.
-- Darren Duncan
be able to port
the subclass to DBIv2, without any additional burden on DBI
developers.
I accept your challenge.
-- Darren Duncan
, or whatever
wrapper modules, or whatever attendees want, really.
-- Darren Duncan
--
Title of proposed BOF:
Describe the people who would be interested in attending this BOF:
Which evenings(s) are you available to host your BOF?
Full
previous statement, I may try to have some visuals
after all, rather than this being all spoken.
Thank you. -- Darren Duncan
on a wider scale.
-- Darren Duncan
--
Summary of my perl5 (revision 5 version 8 subversion 7) configuration:
Platform:
osname=darwin, osvers=7.9.0, archname=darwin-2level
uname='darwin darren-duncans-computer.local 7.9.0 darwin kernel
version 7.9.0: wed mar 30 20:11:17 pst
in time. It also appeared that part of Makefile.PL
one was a reverse, which contributed to the rejections.
-- Darren Duncan
, it has the same effect as saying a normal connect() plus an
explicit 'start'.
-- Darren Duncan
At 12:04 PM +0100 5/26/06, Tim Bunce wrote:
http://www.data-plan.com/public/DBI-1.51-RC1.tar.gz
I tried the standard install routine on my own installation of perl,
v5.8.7 built for darwin-2level. The DBI tests worked as per usual.
-- Darren Duncan
to actually use it though. -- Darren Duncan
no-thread on Mac OS X 10.4.6 PPC. -- Darren Duncan
of DBI-1.53-RC2 showed all tests successful. I did not actually try
to use DBI in an application, though. -- Darren Duncan
present.
-- Darren Duncan
At 9:17 AM + 2/2/07, Tim Bunce wrote:
On Thu, Feb 01, 2007 at 10:26:09PM -0800, Darren Duncan wrote:
install_driver(Gofer) failed: Base class package
Class::Accessor::Fast is empty. (Perhaps you need to 'use' the
module which defines that package first.)
Ah, thanks. I'd planned
.
Yup, that made a big difference. All tests pass. I did not actually
try to use it or compile any DBD against it, though. -- Darren Duncan
actually try to install DBI, and I didn't test any
DBD or programs with it.
-- Darren Duncan
they'll be portability issues with some gofer transports.
A simple 'make test' fails on my machine (Perl 5.8.8 no threads, Mac
OS X 10.4.8 PPC, GCC 4.0.1) citing various problems with Gofer.
Details appear below this email.
-- Darren Duncan
--
darren-duncans-power-mac-g4:/Volumes
At 10:13 AM + 2/17/07, Tim Bunce wrote:
On Fri, Feb 16, 2007 at 08:26:57PM -0800, Darren Duncan wrote:
A simple 'make test' fails on my machine (Perl 5.8.8 no threads, Mac
OS X 10.4.8 PPC, GCC 4.0.1) citing various problems with Gofer.
t/85gofer.
# Failed test
At 9:51 PM + 2/17/07, Tim Bunce wrote:
On Sat, Feb 17, 2007 at 03:22:14AM -0800, Darren Duncan wrote:
So I updated t/85gofer.t and re-ran 'make test'.
This time, I just showed the output of testing t/85gofer.t rather
than the whole test suite.
FYI, the Perl I ran the original DBI
://homepage.mac.com/tim.bunce/.Public/perl/DBI-1.54-RC5.tar.gz
... as the other spelling just gets you RC4 again.
Anyway, RC5 fixes the problem for me; all tests pass.
-- Darren Duncan
not actually tried to use any of the above with my own
application code, however, nor am I currently equipped to do so.
Maybe in a few months.
-- Darren Duncan
At 11:36 AM + 2/22/07, Tim Bunce wrote (off-list):
On Wed, Feb 21, 2007 at 09:22:32PM -0800, Darren Duncan wrote:
At 1
At 2:46 PM +0100 4/13/07, Tim Bunce wrote:
You can download it from
http://homepage.mac.com/tim.bunce/.Public/perl/DBI-1.55-RC1.tar.gz
DBI's make test were all successful or skipped with Perl 5.8.8,
with no threads, under Mac OS X 10.4.9. -- Darren Duncan
of the SQL 2003
Documents zip file, linked to near the top. -- Darren Duncan
At 3:02 PM +0100 4/27/07, Tim Bunce wrote:
You can download it from
http://homepage.mac.com/tim.bunce/.Public/perl/DBI-1.55-RC2.tar.gz
All tests of just DBI itself pass or skip on my system, Perl 5.8.8
with no threads, gcc 4.0.1, Mac OS X 10.4.9 PPC. -- Darren Duncan
,
so having less indirection for implementing the language over existing
DBMSs should only be helpful. Also as commented, the solution should
support inputing or returning arbitrary configurations of data, eg,
multiple subject-to-update parameters, as SQL itself supports. -- Darren Duncan
to include in DBD::SQLite::Amalgamation if appropriate. -- Darren Duncan
Tom Browder wrote:
After looking at various modules for using SQLite, I've not found
exactly what I'm looking for. I want a pm that is higher level than
what I see in DBS::SQLite.
I would like to see functions similar to what
my place.
Matt, thank you in advance for a quick reply.
To everyone, please don't actually submit patches to me until I announce that
I'm ready to receive them, or just send them to RT as you already were.
-- Darren Duncan
.
excelent idea to use Audrey Tangs nameing convention.
I have been stuck back at 3.4 for various issues.
I do Perl and C and offer some help.
Okay and thank you.
-- Darren Duncan
of departure, but DBD::SQLite could also go the way you say. I think this
is an idea best discussed on dbi-dev or if you want to prototype and present
your idea there please do so. There are probably other issues to consider that
people may bring up.
Thank you. -- Darren Duncan
DBD::SQLite. I currently
estimate mid-March to get into it.
-- Darren Duncan
Erik Aronesty wrote:
I do Perl and C and offer some help.
Same here. I feel reasonably at home both in C and Perl, and I've
written some simple XS code. I don't have any experience with DBI,
I will also do what I
on utsl.gen.nz or
github or both, so I can receive patches by pulling from someone's fork. Its
not up yet though.
Thank you in advance for any feedback.
-- Darren Duncan
, and continues to do so, I'm the happiest, but so far he
isn't. And my email attempts have failed at a response.
So, should I try to phone Matt now?
Thank you. -- Darren Duncan
Cosimo Streppone wrote:
In data 27 marzo 2009 alle ore 03:30:10, Darren Duncan
dar...@darrenduncan.net ha scritto:
So, out of my un-paid projects, my promise to take over release
management of DBD::SQLite (from the still incommunicado previous
owner) has now come to the front of my queue (now
is discussing this work so I can
join it. And I look forward to a CPAN release. Or in helping you do it.
Thank you. -- Darren Duncan
Steffen Mueller wrote:
Hi Darren, hi Matt,
Matt, I hope you're well and simply too busy to answer!
Darren Duncan wrote:
Following up a discussion a couple months ago
David E. Wheeler wrote:
On Mar 27, 2009, at 2:39 AM, Darren Duncan wrote:
I have tried emailing Matt several times without response already.
Should I try telephoning him next? For all it looks like, Matt has
abandoned the module. If someone knows better, or has been in contact
recently
::SQLite are expected to come out separately from and after the
stabilized switch to the amalgamation sources.
Please do not reply to me directly with your responses. Instead send them to
the forums or file with RT as is appropriate.
Thank you. -- Darren Duncan
.
Please do not reply to me directly with your responses. Instead send them to
the forums or file with RT as is appropriate.
Thank you. -- Darren Duncan
if
there are none, and commit()/rollback() ends the innermost transaction.
This all said, if you still want to have actual named savepoints, well David's
proposal sounds fairly decent.
-- Darren Duncan
David E. Wheeler wrote:
Tim et al.,
Anyone given any thought to an interface for savepoints? They're
changing nothing in DBI is actually the
best approach concerning savepoints. -- Darren Duncan
);
SQLite also has savepoints, since 3.6.8 around January.
See http://sqlite.org/lang_savepoint.html for details.
SQLite:
SAVEPOINT $name
RELEASE [SAVEPOINT] $name
ROLLBACK [TRANSACTION] TO [SAVEPOINT] $name
Adding that to DBIx::Class shouldn't be difficult.
-- Darren Duncan
for DBI itself to use those semantics (but it hadn't already).
-- Darren Duncan
with your responses. Instead send them to
the forums or file with RT as is appropriate.
Thank you. -- Darren Duncan
with your responses. Instead send them to
the forums or file with RT as is appropriate.
Thank you. -- Darren Duncan
in a local file; this file is
named by the user when connecting. I think that #2 is the best option for that.
-- Darren Duncan
of mandating declared versions and
go from there.
-- Darren Duncan
, call it 1.613_1 or 1.613_001 or
such.
Does that not make more sense?
-- Darren Duncan
updateable by the public; posting in the list can
cause an update there by a registered SQLite developer).
Please do not reply to me directly with your responses. Instead send them to
the forums or file with RT as is appropriate.
Thank you. -- Darren Duncan
like the fix should be some relatively simple symbol renaming.
I could probably do this, but not until at least a few days from now when I have
more time to do that *and* test it.
-- Darren Duncan
Tim Bunce wrote:
What's the state of play?
Will DBI 1.614 still lack the POLLUTE or did you put that back in? -- Darren
Duncan
it much easier to test that drivers are correct if DBI
isn't muddling things up by perpetuating the pollution. -- Darren Duncan
to be the case.
Guidance please. Thank you.
-- Darren Duncan
Tim Bunce wrote:
Short version:
Please download build test *and install* DBI 1.613_71, then download build
and test any compiled drivers you use to check they work with DBI 1.613_71.
Let us know about any failures *and* successes
query language initially as per
your plan. If the ability to query in SQL is desired then you can provide that
as an alternative, but under no circumstances should the ability to use the
DBMS' native query language be denied as an option to users.
-- Darren Duncan
Darren Duncan wrote:
Rudy Lippan wrote:
Does anyone know if there are any DBD::drivers that do not use some
variant of SQL? I ask because I am planing on implementing the driver
using mongoDB's native query language initially, but having a
query_language attribute so that It would be possible
Rudy Lippan wrote:
On 11/03/2010 10:08 PM, Darren Duncan wrote:
Darren Duncan wrote:
Rudy Lippan wrote:
Does anyone know if there are any DBD::drivers that do not use some
variant of SQL? I ask because I am planing on implementing the driver
using mongoDB's native query language initially
Is it necessary for each DBI driver to have a prefix registered in DBI itself,
or is this only necessary when the driver wishes to expose extra public methods?
If the DBD doesn't expose custom methods, can it be used without the prefix
registration? -- Darren Duncan
with trans-ASCII
characters, we have to account for those too, making sure that the various
Perl-side code correctly matches or doesn't match those identifiers, and so on.
-- Darren Duncan
query what version(s) of the DBI spec
the DBD provides.
So what say you?
-- Darren Duncan
other kinds of changes to a minimum, to aid transition, and then other API
changes can happen later, with new API versions.
-- Darren Duncan
Darren Duncan wrote:
To be brief, ...
I don't know if this has come up in past discussions about the next
major DBI version, but I'll say it now, since
checking all available packages on the system, well that solution
could also exist as said external DBI utility function.
-- Darren Duncan
David Nicol wrote:
On Mon, Sep 12, 2011 at 3:13 PM, Darren Duncan dar...@darrenduncan.net wrote:
So what say you?
I think you can do this without any change to DBI.
You have your own DBI-like framework; you could declare that anything
that passes your conformance suite
is compliant
David Nicol wrote:
On Mon, Sep 12, 2011 at 5:20 PM, Darren Duncan dar...@darrenduncan.net wrote:
How mandatory, currently, is the mandatory shared codebase? Are
there really traps and snares preventing
a different framework from using DBD modules? I'm presuming that there
aren't; ICBW.
So
can choose to create a new DBD that just works the
new/inverted way, and users can use that and legacy DBDs at the same time.
-- Darren Duncan
1 - 100 of 150 matches
Mail list logo
