Hi Fabian,
I just got my new workstation and it is an AMD64 machine with windows64
installed.
I also got myself both the microsoft 64 bits compiler as well as the intel
64 bits compiler. With the particular goal of course to port MonetDB.
I am not promising any timeframe but if we don't have a native windows64 port
in the next couple of months I would be very surprised if not disappointed.
Peter
>>
>>
>>
>> Just a small note. I don't have any windows building experiences, but
>> we currently don't have access to such box running that operating
>> system. As far as I can tell, there is no real priority to do so
>> either. There are build instructions for windows, but it is unknown how
>> 64-bits are enabled and if this will compile and run. This seems an
>> unexplored area to me.
>>
>> Regards,
>> Fabian
>>
>>
>> Cardillo Raymond A Civ AFRL/IFEA wrote:
>> > Has anyone out there taken the time to build an MSI for the AMD64 versions
>> > of Windows? The x64 version of Windows was released a few months ago and
>> > was available in Beta for a while, so I'm hoping someone has either done
>> > this already, or can provide some advice on how to build/compile for this
>> > platform. Anyone know of future plans to make this one of the standard
>> > platform builds? Windows x64 is only going to grow in popularity from here,
>> > especially amongst researchers and others who can benefit from 64 bits.
>> >
>> > Thanks for any info,
>> > Ray Cardillo
>>
>>
>>
>>
>>
I'd like to add a more perlish layer around MapiLib (working title:
MonetDB::CLI). This may look like:
my $Cxn = MonetDB::CLI->connect( ... );
my $Req = $Cxn->query('select * from env');
while ( my $Cnt = $Req->fetch_row ) {
print $Req->fetch_field( $_ ) for 0 .. $Cnt-1;
}
Still much in the spirit of Mapi, but handles are now objects (with
destructors), functions are methods and the methods can throw exceptions.
Once we have such an interface, additional implementations are possible.
For instance, a XS module could skip the MapiLib layer and use libMapi
directly. Later on, an implementation for MCL will be added (I hope) -
either in pure perl or on top of libMCL (in case such a library will
emerge).
Of course, I'd like to use this new interface from DBD::monetdb to be
able to choose between various implementations and to ease the
transition to MCL.
On the downside: additional modules means additional installation efforts.
Especially the people resposible for the RPM's will be affected.
If this sounds too screwy, it's now the chance to stop me ;-)
Steffen
Niels Nes wrote (2005-07-16 14:57):
> I guess we never told you that we all agree this is a very good idea. We
> have similar plans with the jdbc and php/pear-db interfaces. So go ahead.
O.k., FYI, I registered the 'monetdb_' prefix within DBI:
<http://www.xray.mpe.mpg.de/mailing-lists/dbi/2005-08/msg00102.html>
As soon as Tim commits this patch, you'll see it here:
<http://svn.perl.org/viewcvs/modules/dbi/trunk/DBI.pm?view=log>
Further on, I proposed DBD::monetdb for inclusion in the Module List
<http://www.xray.mpe.mpg.de/mailing-lists/modules/2005-08/msg00695.html>
Usually, this takes time. (Somebody of the module list maintainers has to
acknowledge the proposal.)
Certainly, DBI users expect to find a DBI driver on CPAN:
<http://search.cpan.org/modlist/Database_Interfaces/DBD>
Do you have any objections that I upload snapshots of DBD::monetdb to
CPAN?
Such a package will be generated as follows:
cd MonetDB/src/mapi/clients/perl/DBD
Makefile.PL
make dist
I'm aware that currently, with its MapiLib dependency, the package
isn't very useful on its own - the user needs a MonetDB client anyway.
That's not nice, but nothing out of the ordinary (and it may be changed).
Steffen
Hello,
I am trying to use MonetDB as a backend for Java application I am developing.
I have noticed that inserts the application does have no effect.
Statements are executed without exceptions, but data rows do not get into table.
I have investigated the problem and have figured out that problem is
in transaction and savepoint handling. If transaction had savepoints,
it could be silently rolled back when Connection.commit() is called.
I have finished with short Java program that demonstrate the bug(?), I
am attaching it to the message. Please, take a look.
I tested with MonetDB-4.8.2+sql-2.8.2 (release, source tarball) and
with MonetDB-4.8.3+sql-2.8.3 (nightly build, August 30).
Platforms: 32-bit Linux RedHat 9, 32-bit Linux Ubuntu 5.04
--
Best regards,
Andrei Martsinchyk mailto:andrei.martsinchyk@gmail.com
I just installed the windows version of MonetDB and tried to follow the
Tutorial on Mknife but was unable to connect. Looking at my system neither
of the files /infosets/MILinfoset.xml;/infosets/MILdemo.xml
where created nor where the directories. Is this a know issue?