On 06-02-2008 11:49:49 +0100, Michael wrote:
But sending io.print("hello"); with JDBC resulted in:
Database connect failed: InvalidCredentialsException:checkCredentials:Invalid cr edentials for user 'monetdb'
This means you entered a wrong password (or the authorisation tables are corrupted).
C:\Programme\CWI\MonetDB5\share\MonetDB\lib>java -jar jdbcclient.jar -umonetdb - lmal password:
Your second try appears to work, though.
Welcome to the MonetDB interactive JDBC terminal! Type \q to quit, \h for a list of available commands auto commit mode: on monetdb-> io.print("hello"); Error: TypeException:user.main[1]:'ioo.print' undefined in: _1:any := ioo.print( _2:str) monetdb->
This is really weird. First and foremost this query will never work correctly using JDBC (you will witness JDBC complaining about protocol violations). Please realise that you use an undocumented hack that we cannot support.
What really worries me though is the "ioo.print" instead of "io.print", which appears to be entered.
Reading your other posts, I don't really understand what you want. While I think anything is better than OpenLDAP, how do you see MonetDB fill in the functionality here? I guess you could simply define some SQL-based database schema to do the LDAP equivalents, but for instance pam_ldap/nss_ldap will expect to speak the LDAP dialect/language, which somehow needs to be mapped onto any language that MonetDB supports. Doing this in Java will not be desirable for the memory footprint involved in doing so. Unless you have completely different objectives here, I think Java is not what you are looking for.
I would be very pleased if there would be an LDAP language frontend to MonetDB. That is, MonetDB supporting the ldap and ldaps protocols. Of course the MonetDB that you would use there is a specially compiled/crafted version that has a very low footprint and excludes any functionality that is not necessary, basically just libgdk.