it all comes down to invoking the information scheme provided by the database, which is a set of tables and / or views that you can select, which then return data about tables, columns, and everything else.
In the case of Sybase, they really have a very tight format for their information scheme (mainly because of the 16 + 16 column format for representing the foreign key constraint ), so when I created the Sybase dialogs, I left some of the reflection in the "todo" work. There is no technical reason why this is impossible to do, it is just a long and tedious job, and so far we practically do not use Sybase dialogs.
If you want to work out some basic queries to get table and column names, we can pass them directly to SQLAlchemy. The scheme you will work with is documented in this section: http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.tables/html/tables/tables2. htm and there you will watch sysobjects , syscolumn and sysreferences .
source share