> Either instead of setting the id for both sides of the ManyToMany
> > relationship as Group_id, should it not do Group_id1 and Group_id2, or
>
> Good point, I hadn't consider many-to-many between the same class.
>
> > And we need a way to redefine an existing table, at the very least to
> > add columns to it so I do not have to save out and re-enter my data
> > every time I make a change. Even something like setting a static
> > version number to the entity class along with a function that lets me
> > describe change from version to version would be perfect, then I can
> > say what to remove, what to add, how to reformat something, etc...
> > propagating all the way through the changes.
>
> Yes we need that. But we need ideas to keep this simple too.
>
>
Is Wt::Dbo intended for the problem space where the programmer controls the
database? Or is it
intended as a general purpose RDBMS manipulation and access interface.
The fact that Wt::Dbo automatically does schema creation entails
that it includes schema and schema object creation policy.
- Could you spell out the Wt::Dbo policy for database management is?
- Should database constraints now be handled by Wt::Dbo?
- Should database access control be handled through Wt::Dbo?
- Triggers & stored procedures anyone?
- Is it appropriate for the DBA to manipulate the Wt:::Dbo database schema
objects without using Wt::Dbo?
I fair that Wt::Dbo is a way for Emweb to make other peoples mistakes (see
this thread for example),
all over again. All to the detriment of the still not finished core Wt
functionality.
Kind regards,
Maurice 'wishing Wt would do one thing and do it well' Gittens
> Regards,
> koen
>
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> witty-interest mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
