Tutorials & Manuals » SQL Yoga » Telling SQL Yoga When Your Database Schema Changes
Topics
- Introduction 1
- SQL Yoga Primer 3
- Notes on Error Reporting 3
- General Concepts 4
- Database Objects 5
- Database Connections 5
-
SQL Query Objects
6
- Introduction to SQL Query Objects
- Creating A SQL Query Object
- How Do I Create Records In a Database Table Using a SQL Query Object?
- How Do I Delete Records From the Database Table Using a SQL Query Object?
- How To Use Cursors With a SQL Query Object
- How Can I Convert a User Search String Into An AND/OR Search When Generating a Query?
- Record Objects 5
- Table Objects 4
- Table Relationships 3
Other Resources
How-tos
- Lessons
- Signing Your Applications and Building Installers
GLX Application Framework
- GLX Application Framework 1.1
- Converting An Existing Application To Use The Framework
SQL Yoga
- SQL Yoga
- SQL Yoga Examples
- SQL Yoga To-Do Application
- SQL Yoga IDE Plugin
Plugins, Externals and Libraries
- Plugins
Comments
0 for this lesson
Telling SQL Yoga When Your Database Schema Changes
Now we have covered everything you need to do to get SQL Yoga up and running in a stack. You may recall that SQL Yoga provides much of the functionality that it does because it stores information about the tables and columns in your database. Because of this, it is important that you let SQL Yoga know if you add or delete tables and columns from your database.
Telling SQL Yoga to Reload Database Schema
Execute the following handler in the message box to update the schema stored in the database object:
dbobject_reloadSchema
put the result
Save Your Work
After reloading the database schema you should save your work by calling dbobject_save in the message box and then saving your stack.


Add your comment