Zugg Software :: View topic

Posted: Mon Oct 12, 2009 11:05 pm

One of the features I've been working on that is important for TeSSH is adding SQL commands. This should also benefit CMUD users. I'm still trying to decide if this will only be a CMUDPro feature, or if I'll make it a normal part of CMUD.

The syntax is currently very simple. It's a two step process to use a database: 1) Declare the database, 2) Execute a query.

To declare a database, you can use either the #SQLDB command, or the %sqldb function. The difference is that the %sqldb function actually returns a database connection object (the same syntax as documented in zApp). Whereas the #SQLDB command creates a "named" connection but doesn't actually return any object. Normally you will use #SQLDB to assign a nice name to the connection. The syntax is:

#SQLDB Name Database Driver Server Port Username Password

where everything accept the Name is optional. If you only use a single argument, it is assumed to be the Database name (of a local database file) and the Name is given by the part of the filename up to the period. For example:

#SQLDB muds.db

will open the "muds.db" local database file and create a named connection called "muds".

The Driver defaults to SQLite3 (or SQLite2 if you reference an existing SQLite2 file format). The same list of database drivers supported in zApp can be used here.

Once a database connection has been defined, you can then execute an SQL query using the %sql function. The syntax is:

%sql(connectionName,SQL)

where connectionName is the name of the #SQLDB opened previously. The result of %sql is a zApp Query object. Most of the methods and properties of the zApp object are supported.

Here is a quick example of how you would loop through the MUD list database and display the title of each MUD:

Posted: Tue Oct 13, 2009 3:02 pm

Very cool Zugg!, but right as im getting pretty good with lua/luasql :(

Couple questions,

This sounds like your porting the whole db portion of zapp over to Cmud, how will you be handling then events of the Query object? As global events? or something more like Queryname.OnDeleted = { code to execute}? really the one that interests me most is the connection.OnCreate event, would save a lot of error checking code.

the zs.getmodule can retrieve the map module, but i was unable to find any ismap property or map property to assess the map filename /file path, could this be added?

Other questions got answered as I re-read the zapp documentation or will be answered as i play with the beta release.

Additionally, the zapp documentation viewer... doesn't appear to be vista friendly, I couldn't get it to run kept getting windows xxx application has stopped working messages.

This also sounds very much like a Cmud pro feature, It offers much of the capability of zmapper if you know what your doing, plus so much more.

Posted: Tue Oct 13, 2009 5:12 pm

No events at this time, sorry. Maybe when the full zApp gets added to CMUD someday. But the event handling was done by the zApp core, which is not part of CMUD right now.

For the map file, try %pref(mapfile) and see what that says. I agree that a better way to get the database name from the actual Map Database object will be needed at some point.

zApp was never Vista friendly. It was one of the reasons (and lack of any sales) that caused zApp to be abandoned. Since the database portion of zApp was not a "visual" component, it was relatively easy to port over. You can still view the zApp documentation in your web browser HERE. No plans to update the zapp documentation viewer.

Posted: Wed Oct 14, 2009 2:13 am

Sounds like a good feature Zugg. I agree with wrym that this sounds like a Pro feature.