On Fri, 4 Jun 2010, Alexander Foken wrote:
Right. (But remember that DBI was there before Unicode support was added to
Perl, and also most DBDs are older that the Unicode support. Before Unicode
was there, you just passed bytes around and everything just worked.)
Only if by everything you exc
On Thu, 3 Jun 2010, Alexander Foken wrote:
Really strange way to avoid pack()/unpack(). At least, you can get rid of the
Yes, yes, this is hack code, not production.
... should just work. It doesn't quite, because the hex string is not just a
dump of a 16 Bit Unicode encoding, but it is a UT
On Thu, 3 Jun 2010, Michael Peppler wrote:
2010/06/03 14:08:11 unicode CRITICAL: FATAL: DBD::Sybase::db do failed: Server
message number=2402 severity=16 state=1 line=1 server=HDATADEV1 text=Error
converting characters into server's character set. Some character(s) could not
be converted.
I'
On Thu, 3 Jun 2010, Dave Rolsky wrote:
If I _don't_ set that, the data goes in and comes out as bytes, rather than
the bizarro hex string. However, the data does have the utf8 flag set when it
comes back from Sybase, so I have to run it through Encode::decode.
Doh, the data _does not_
On Thu, 3 Jun 2010, Michael Peppler wrote:
Which version of Sybase, which version of Sybase OpenClient, and which version
of DBD::Sybase?
Ah, I was using the old libs (11.0), which may have been the problem. I
was also using DBD::Sybase 1.07.
I switch to Sybase 15.0 (OCS 15.0 if that makes
On Thu, 3 Jun 2010, Michael Peppler wrote:
I just gave this a try - I'm under linux, with ASE 15.5. I created a table with
a univarchar column, entered some data via isql, then wrote a minimal perl
script to fetch the data.
If I use a UTF8 locale (i.e. LANG=en_us.UTF8) I get the correct outpu
I'm working on an i18n project, and we use Sybase (sigh).
Newer versions of Sybase have built-in support for Unicode with the
univarchar (and other uni*) type.
However, it seems like DBD::Sybase doesn't have any support for this.
Specifically, if I take a Perl unicode string (utf8 flag is on)
0.87 May 14, 2005
BUG FIXES:
- Table names in CREATE INDEX statements for Postgres were not quoted.
- Database names in CREATE/DROP DATABASE statements for Postgres were
not quoted.
- Postgres database names with upper case characters were never being
detected as being instantiated, which meant Al
0.86 December 22, 2004
BUG FIXES:
- Allow a UNIQUE constraint as a column attribute for MySQL.
ENHANCEMENTS:
- It is now possible to use a single Alzabo schema object to create
and access multiple copies of that schema in an RDBMS. This is done
by setting the "schema_name" parameter whenever call
0.85 October 12, 2004
BUG FIXES:
- The DECIMAL and NUMERIC column types in MySQL were not being treated
as numeric types. This meant that you couldn't give such a column the
UNSIGNED attribute, among other problems. Reported by Bob Sidebotham.
- If a column had CHECK constraints, the Postgres
0.84 September 4, 2004
ENHANCEMENTS:
- Alzabo::MethodMaker will now warn you when you it creates a method
that overrides a parent class's method. This can cause problems when
you override the table class's name() method with one that returns a
column object.
BUG FIXES
- Make Alzabo::Create::
0.83 June 9, 2003
MISCELLANEOUS:
- I got fed up with the instability of CVS on Sourceforge, and am now
using a Subversion repository I host myself. See "source" page on
www.alzabo.org for details.
ENHANCEMENTS:
- All SQL-generating methods for the Alzabo::Runtime::Schema and
Alzabo::Runtime:
Here's a simple recipe to reproduce this:
my $dbh = DBI->connect(...);
print "overloaded\n" overload::Overloaded($dbh);
The error that comes out is:
can: handle 'DBI::db' is not a hash reference at dbi.pl line 9.
This is coming from DBI, because the Overloaded function looks like this:
0.82 January 6, 2003
ENHANCEMENTS:
- The Alzabo::Runtime::Table->insert() and
Alzabo::Runtime::InsertHandle->insert() will not create a new row
object when called in void context. This should make inserts faster
when you don't need a row object back.
- When reverse engineering a MySQL schema,
0.81 December 21, 2003
ENHANCEMENTS:
- Added a new insert handle feature, which should be significantly
faster for batch inserts than repeatedly calling the table class's
insert() method. Development funded by Marigold Technologies.
BUG FIXES:
- An order_by parameter that contained two SQL fu
Well, here it is. The big 0.80 release. Please note that this release
has quite a number of backwards incompatibilities. The biggest of these
is that the old caching system is gone. If you were using it, you won't
get an error when you load it, because the modules will probably still be
on your
0.79_03 October 18, 2003
ENHANCEMENTS:
- Many doc rewrites and updates.
- Documented row state classes.
- Added back the no_cache parameter to avoid caching one or more rows.
- Moved the relevant documentation from Alzabo::Runtime::PotentialRow
into Alzabo::Runtime::Row.
BUG FIXES:
- Fixed
Another beta before 0.80. I'm still looking for feedback on the docs.
Special thanks to Kineticode for funding some of the development done for
this release.
0.79_02 October 17, 2003
ENHANCEMENTS:
- Added support for table attributes like MySQL's "TYPE = ..." or
Postgres's "WITH OIDS".
- Ad
This is a dev release for the hopefully soon 0.80 release. There's been a
_lot_ of changes, so if people could test this and report back I'd be very
grateful. There's also some features I might try to add before 0.80,
notably table update & delete, but those don't seem that urgent.
I'd also appr
Since there seem to be a few persistent bugs (particularly one that's new
with Perl 5.8+), I'm release 0.73 as a bug fix release. I'm still working
0.80, which will have many more feature additions, and bug fixes, but
hopefully this release will at least let people install Alzabo under Perl
5.8.0.
On Sat, 13 Sep 2003, Jeff Urlwin wrote:
> I'd *highly* recommend installing the latest MDAC (2.7?) from Microsoft on
> both the server and the client (security reasons for the server and correct
> working queries on the client. If that still shows the problem, let me
> know. I don't see it here
DBD::ODBC 1.06, DBI 1.37, SQL Server 2000, whatever ODBC drivers come with
Win 2000 (SP3) (probably 2000.81.9030.04)
Whenever datetimes are returned from a SQL statement, they end up looking
something like:
3/3/2020 12:00:00 A\0
Anyone have any idea why this would happen? Integer and varchar f
I found a bug in the ->tables method. It includes all the system tables.
A patch is at the bottom of the message.
The SQL was correct in 1.13 so I'm not sure how this happened. There's
also no real test of this method in the test suite, other than testing to
make sure that calling it doesn't die
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse engi
On 29 Sep 2002, Randal L. Schwartz wrote:
> I got a casual (in-person) report last night from a user at a
> conference I was attending that Perl 5.8.0 appeared to be incompatible
> with DBD::MySQL. Now, I couldn't personally confirm or deny this,
> since I use Pg exclusively now. Does anyone ha
What, almost two months between releases?! I must be slowing down.
Vacations will do that to you.
This release corrects a rather nasty bug in the schema creation side of
Alzabo, as well as a number of other bugs.
Alzabo is a program and a module suite, with two core functions. Its first
use is
[ Gah, the installer in 0.66 was a bit broken. This release fixes it. ]
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. o
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Thu, 6 Jun 2002, Tim Bunce wrote:
> =head2 Changes in DBI 1.25,5th June 2002
>
> Fixed $dbh->{Driver} and $sth->{Statement} for driver internals
> These are 'inner' handles as per behaviour prior to DBI 1.16.
Works for me. Thanks, Tim.
-dave
/*==
www.urth.org
we
It looks like something in DBI 1.24 broke $dbh->func.
If I try to call this:
$dbh->func( 'createdb', 'foo', 'admin' )
I get an array message about being unable to call func on an undef value
at DBD::mysql line 217.
sub admin {
my($dbh) = shift;
my($command) = shift;
my($dbname) =
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Mon, 1 Apr 2002, Marcus Claesson wrote:
> > Why are you trying to put a backslash in there. DBI is not the psql tool!
> > Get rid of the backslash.
>
> The reason for using \COPY here is that you otherwise have to be superuser to
> copy (with the plain COPY) the data into a created table. I'm
On Thu, 28 Mar 2002, Marcus Claesson wrote:
> > perl -e '$a= "\Copy"; print "$a\n";' > Copy
>
> You're right about that perl loses the '\'.
> But when I try to escape the backslash by typing
> $dbh->do("\\COPY table FROM 'file.dat'");
> I get this message:
> DBD::Pg::db do failed: ERROR:
On 18 Feb 2002, Jeff Boes wrote:
> Is it true that RowCacheSize has no effect with the DBD::Pg driver? The
> DBD::Pg doc just says that it's "Implemented by DBI, not used by
> driver", which implies that DBI actually does something by default.
I believe the "Implemented by DBI" phrase simply me
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Thu, 14 Feb 2002, Bryan Tolka wrote:
> if ($ip ne $oldip){
> $sth = $dbh->prepare("update ipmgt set
> ip = '$oldip'
> hw = ,
> dnsName = ,
Um, you can't just leave it empty!
Use bound values (read the DBI docs for info on placeholders). This is
much e
On Wed, 6 Feb 2002, Tim Bunce wrote:
> How does this sound:
>
> =item C (code ref, inherited) I
>
> This attribute can be used to provide your own alternative behaviour
> in case of errors. If set to a reference to a subroutine then that
> subroutine is called when an error is det
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Fri, 11 Jan 2002, Philip Molter wrote:
> The only downside you're going to find are the down/upsides of
> switching from MySQL to PostgreSQL. The DBI interface won't change
> for you. My personal experience between the two databases is that
> MySQL is easier to manage, easier to work with, a
On Fri, 4 Jan 2002, Simon Oliver wrote:
> What I like is the fact that it will be integrated into core DBI and promote
> the use of this subclassing mechanism as a basis for writing cross-platform
> code rather than each modules reinventing the wheel (c.f. Alzabo).
Yep, I'm thinking that I'll co
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Mon, 10 Dec 2001, Matisse Enzer wrote:
> DBI/Wrapper version 0.01
>
>
> DBI::Wrapper is a simple module that provides a high-level interface
> to the Perl DBI module. The provided methods are for fetching
> a single record (returns a hash-ref), many records (returns
>
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Mon, 26 Nov 2001, Todd Nemanich wrote:
> 11\:16\:43', '2001-01-17 00\:00\:00', '2001-01-16', 'Phoned re\:mc and
^^ ^^
It thinks those are placeholders. The DBD::Pg module parses placeholders
itself and replaces them before sending the SQL to the RDBMS.
Apparently
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Fri, 19 Oct 2001, David Kirol wrote:
> I want to explore the Alzabo data modeling tool but I cannot find any
> tutorial or how to on the web. Can anyone point me in the right direction?
Someone also mentioned the Linux Journal article, which is a good start.
Also, check out the docs at http:/
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Wed, 26 Sep 2001, Wilson, Doug wrote:
> There's an article on Alzabo in this months
> Linux Journal. Its also online, just go to
> http://www.linuxjournal.com and click on the
> picture of the magazine, then look in the toolbox
> section of the page.
For the posterity of the archives, its at:
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
I just thought I'd let this list know that there's a comparison of
persistence tools for Perl at http://poop.sourceforge.net. POOP stands
for Perl Object-Oriented Persistence. There's also a mailing list for
discussion of such things ([EMAIL PROTECTED]).
The document as it stands compares a num
On Wed, 29 Aug 2001, Alex Krohn wrote:
> If I use mysql, or Oracle, as a driver, it works as expected. I searched
> through the list, and the only answer seemed to be to use placeholders,
> which isn't really an option in my situation.
Why are placeholders not an option? They're generally a goo
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Thu, 9 Aug 2001, Giotto De Filippi wrote:
> Can I do SQL background queries with DBI?
>
> like instead of doing ->prepare, ->execute and ->fetchrow_hashref something
> like ->is_ready, to do before fetchrow, so for example I could do other
> things with my perl program while it's waiting for t
On Wed, 8 Aug 2001, Matt Kent wrote:
> I have a MySql database (ver3.23.39a), Perl 5.6.0, and Apache 1.3.12.
> I am looking for a tutorial on how to use the DbFramework module, if there is
> any. If not some source code of something using the module would also be good.
> I'm using MySql as the da
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Tue, 17 Jul 2001, Chabowski wrote:
> I'm testing mason for the first time on our servers, and although mason
> itself is working, I can't seem to get it to recognize DBI. I have
> included "use Apache::DBI;" in my handler.pl file. I have to say I'm a
> novice with DBI, so I'm probably doing
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Fri, 29 Jun 2001, Nate Mueller wrote:
> (in cleanup) dbih_getcom handle 'DBI::st=HASH(0x880e950)' is not a DBI
> handle (has no magic)
This happens when a DBI handle is serialized (or if you try to use a
previously valid DBI handle after a fork). SOAP is somehow serializing
your handle. The
On Thu, 21 Jun 2001 [EMAIL PROTECTED] wrote:
> Since my last 2 posts prompted absolutely no replies whatsoever my question
> is simply this:
>
> Has anyone implemented DBIx::AnyDBD?
>
> I realize that this isn't specifically a DBI question, but the perldoc
> documentation for DBIx points to thi
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
On Thu, 3 May 2001, David H. Silber wrote:
> I've also stumbled upon DBIx::DBSchema, which is supposed to help me
> extract schema information from a database.
>
> Does anyone know how Alzabo & DBIx::DBSchema compare? Or do they
> compare at all?
>
> What I need is to get the complete schema and
On Thu, 3 May 2001, Bob Gustafson wrote:
> There is an interesting project on sourceforge called Alzabo, which
> provides an html database interface using DBI, Perl with mason and
> mod_perl/apache for both design and browsing of database tables. It uses
> mysql and/or oracle and/or postgresql.
The recently announce 0.41 release ws missing a file from the tarball.
http://alazabo.sourceforge.net/
Alzabo is a program and a module suite, with two core functions. Its first
use is as a data modelling tool. Through either a schema creation
interface or a perl program, you can create a set of schema, table,
column, etc. objects to represent your data model. Alzabo is also capable
of reverse eng
Alzabo is a program and a module, with two core functions. Its first use
is as a data modelling tool. Through either a schema creation interface or
a perl program, you can create a set of schema, table, column, etc.
objects to represent your data model. Alzabo is also capable of reverse
engineerin
Alzabo is a program and a module, with two core functions. Its first use
is as a data modelling tool. Through either a schema creation interface or
a perl program, you can create a set of schema, table, column, etc.
objects to represent your data model. Alzabo is also capable of reverse
engineerin
Alzabo is a program and a module, with two core functions. Its first use
is as a data modelling tool. Through either a schema creation interface or
a perl program, you can create a set of schema, table, column, etc.
objects to represent your data model. Alzabo is also capable of reverse
engineerin
Alzabo is a program and a module, with two core functions. Its first use
is as a data modelling tool. Through either a schema creation interface or
a perl program, you can create a set of schema, table, column, etc.
objects to represent your data model. Alzabo is also capable of reverse
engineerin
On Sun, 11 Feb 2001, Dave Rolsky wrote:
> I get a slew of these messages when my code finishes running, but only
> when using Perl 5.6.0 (I also tried 5.6.1 trial1).
So I finally tracked this down to a DBI handle passing through Storable's
dclone function. I made this not hap
I get a slew of these messages when my code finishes running, but only
when using Perl 5.6.0 (I also tried 5.6.1 trial1).
Here's a sample:
SV = RV(0x844c874) at 0x844eb94
REFCNT = 1
FLAGS = (ROK)
RV = 0x8458ae4
(in cleanup) dbih_getcom handle 'DBI::db=HASH(0x8458ae4)' is not a
DBI
Alzabo is a two-fold program. Its first function is as a data
modelling tool. Through either a schema creation interface or a custom
perl program, you can create a set of schema, table, column,
etc. objects that represent your data model. Alzabo is also capable of
reverse engineering an existing d
It seems like only yesterday I released 0.30. Oh, I did.
Ok, I found some bugs today and figured it'd be best to get a bug fix
release out.
Here's the changes:
0.31
- Fix bugs in Alzabo::MethodMaker. The insert, update, lookup_table,
and self_relation (parent portion only) were broken.
- A
Alzabo is a two-fold program. Its first function is as a data
modelling tool. Through either a schema creation interface or a custom
perl program, you can create a set of schema, table, column,
etc. objects that represent your data model. Alzabo is also capable of
reverse engineering an existing d
75 matches
Mail list logo
