in order to guarantee column definition consistency I would like to define
my columns in one place, then use them in various tables as objects like
xemployee = StringCol(length=6)
xppid = DecimalCol(size=7, precision=2)
xaction = EnumCol(enumValues=['REG1', 'REG2', 'REG3'])
xhours = DecimalCol(size=6, precision=3)
class Labor(SQLObject):
employee = xemployee
ppid = xppid
action = xaction
...
class Edits(SQLObject):
supervisor =xemployee)
action = xaction
...
I'm not sure what SQLObject does under the hood. Will this work and is it a
good idea, or will I have different tables using common column objects with
wierd results. Would it work if my tables were created from std SQL
statements, and SQLObject used only to reference them.
I apologize for asking a question I could figure out by trial and error, but
I'm still getting my feet wet with SQLObjects and fear doing something that
will corrupt my db in a way that i don't catch initially.
---------------------------------------------------------------------------
The information contained in this message may be privileged and / or
confidential and protected from disclosure. If the reader of this message is
not the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify the sender
immediately by replying to this message and deleting the material from any
computer.
---------------------------------------------------------------------------
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
sqlobject-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
