Am Samstag, den 17.09.2005, 19:00 +0200 schrieb Wolfgang Schaible: > hallo Marc,
Moin Wolfgang, [...] > Subject in 'the' language: How to document a DB structure? > (Tables, Columns, Fields, Types, Length, isAuto, isRequired, > Relations, ...) > my first try: > > > > 'HSQLDB: unusable: shows also deleted DBs and Cols ! > >> > > > sub showDBstruct > > > Dim oTables as Object, oMetaDta as Object, oCols as > > > Object Dim mTablesNames, mColNames, s1, s2, s3, i, j > > > oTables =oDtaSrc.Tables() > > > 'xRay.Xray oDtaSrc 'oTables > > > mTablesNames=oTables.getElementNames() > > > for i=LBound(mTablesNames) to UBound(mTablesNames) > > > s1=s1+">"+mTablesNames(i)+"<"+chr(13) > > > ' oMetaDta=oDtaSrc.getMetaData() 'unimplemented? > > > oCols=oDtaSrc.Tables(i).columns > > > mColNames=oCols.getElementNames() > > > for j=LBound(mColNames) to UBound(mColNames) > > > s3=s3+mColNames(j)+chr(13) > > > next j > > > next i > > > msgbox (s1, 66, "TableNames") > > > msgbox (s3, 66, "ColumnNames") > > > end Sub 'showDBstruct > > > This works fine using DBase or MySQL databases for me (tried > > creating and deleting a table in mysql, it is *not* listed after > > deletion), so I would blame the HSQLDB implementation somewhere > > in the OO.o driver, the jdbc driver or the database itself. > it's not easy to work with OOo-HSQLDB: As i told you, it works with other databases and if it does wrong with HSQLDB it's an error you should file an issue for. > -Docu: same is said in JDK for Java, nearly nothing using Basic > -Documented methods do simply not work (see above) > -No examples There was another thread nearly immediately before this one with the subject "lack of tutorials and documentation", so I think you're right. But as always: it's open source, if you can write some short tutorials or the like about things you have done successfully yet, please do! > > I'd use another approach: making the design using a tool better > > fitting the task could be helpfull. Dia would be a oss candidate > > for this one ... > ok, but now I should made the 'as is' docu, sometimes this differs > from design... :-) > and manually created 'as is' docu differs from reality too > <> With the fact in mind that HSQLDB is used as internal DB engine and should be used as application data store I have to agree here, too. External tools are only valuable if the design is client-server from the start. Since I'm not very used to 1.9 and the 2.0betas: Is the graphical table relations design already back in? This would be the best internal way to get an overview of the underlying databse. If it is not, this would be worth an RFE (every database application has this tool). Heute schon gewählt? Marc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
