I'm not sure at the table level. I know that you need since properly setup at the column level. Bad things can happen if you don't setup since and until correctly (not end of the world bad, but bad).<br><br>However, I do know that schema updates do not take place unless the database version changes in
config.yml. The schema setup script does not check for anything unless the version number recorded in _jifty_metadata differs from that in config.yml.<br><br><div><span class="gmail_quote">On 7/2/07, <b class="gmail_sendername">
Matthew Lenz</b> <<a href="mailto:matthew@nocturnal.org">matthew@nocturnal.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, 2007-07-02 at 09:04 -0500, Andrew Sterling Hanenkamp wrote:<br>> Yeah, if you add a new model to the database, you need to bump the<br>> database version in your config.yml file, or it won't attempt to<br>
> update the database. In this case, you should also define the since<br>> method on your model:<br><br>I've always done that.<br><br>> sub since { return '0.0.2'; }<br><br>Didn't know about this though. Is it necessary? I thought Jifty
<br>examined the current db and applied any missing columns defined in the<br>current model?<br><br>> When developing and you don't want to do that, you need to blow away<br>> the database.<br>><br>> On 7/2/07, Matthew Lenz <
<a href="mailto:matthew@nocturnal.org">matthew@nocturnal.org</a>> wrote:<br>> On Mon, 2007-07-02 at 07:51 -0500, Andrew Sterling Hanenkamp<br>> wrote:<br>> > I can only guess that their's something minute wrong with
<br>> your model.<br>> > Can you post it? If that's not the case, then something<br>> could be wrong<br>> > elsewhere in your app that's causing a failure that's not
<br>> being<br>> > reported. There's also a chance that something about those<br>> plugins is<br>> > broken in trunk.<br>> ><br>> > When schema --setup runs, you should see a line in the
<br>> output like:<br>> ><br>> > INFO - Using App::Model::User, as it appears to be new.<br>> ><br>> > and it should end with:<br>> ><br>> > INFO - Set up version
v0.0.1, jifty version 0.701290<br>> ><br>> > (where your actual version numbers, at least for jifty,<br>> should be<br>> > different).<br>> ><br>> > If you don't see that output, something isn't working
<br>> correctly (or<br>> > you've turned the log level up to WARN or higher, which I'd<br>> recommend<br>> > against during development).<br>><br>> I was able to get it to generate the users table by blowing
<br>> away the<br>> current db and having it regenerate everything. I think that<br>> indicates<br>> that there wasn't anything wrong with the model. I got it<br>> working so
<br>> I'm happy atm.<br>><br>> > Cheers,<br>> > Andrew<br>> ><br>> > On 7/1/07, Matthew Lenz <<a href="mailto:matthew@nocturnal.org">matthew@nocturnal.org
</a>> wrote:<br>> > On Mon, 2007-07-02 at 01:13 +0100, Chia-liang Kao<br>> wrote:<br>> > > 於 日,2007-07-01 於 18:13 -0500,Matthew Lenz 提<br>> 到:<br>> > > > Following instructions in the trunk version of
<br>> > Manual::AccessControl<br>> > > > which details the use of the<br>> Authentication::Password<br>> > plugin. No errors<br>> > > > are returned upon schema --setup but looking in
<br>> the db<br>> > there is no users<br>> > > > table (and the interface confirms the problem<br>> when<br>> > attempting to sign
<br>> > > > up).<br>> > > ><br>> > > > I assume that additional columns are not a<br>> requirement in<br>> > the
<br>> > > > *::Model::User when attempting to use this<br>> plugin?<br>> > ><br>> > > You probably want to use<br>> > Jifty::Plugin::User::Mixin::Model::User from
<br>> > > your user model.<br>> > ><br>> > > Cheers,<br>> > > CLK<br>> ><br>> > Yeah I already have:
<br>> ><br>> > use Jifty::Plugin::User::Mixin::Model::User;<br>> > use<br>> ><br>> Jifty::Plugin::Authentication::Password::Mixin::Model::User;
<br>> ><br>> > Per the instructions in Manual::AccessControl<br>> ><br>> > ><br>> > > _______________________________________________
<br>> > > jifty-devel mailing list<br>> > > <a href="mailto:jifty-devel@lists.jifty.org">jifty-devel@lists.jifty.org</a><br>> > ><br>>
<a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel">http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel</a><br>> ><br>> > _______________________________________________
<br>> > jifty-devel mailing list<br>> > <a href="mailto:jifty-devel@lists.jifty.org">jifty-devel@lists.jifty.org</a><br>> ><br>> <a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel">
http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel</a><br>> ><br>> > _______________________________________________<br>> > jifty-devel mailing list<br>> >
<a href="mailto:jifty-devel@lists.jifty.org">jifty-devel@lists.jifty.org</a><br>> > <a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel">http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
</a><br>><br>> _______________________________________________<br>> jifty-devel mailing list<br>> <a href="mailto:jifty-devel@lists.jifty.org">jifty-devel@lists.jifty.org</a><br>>
<a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel">http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel</a><br>><br>> _______________________________________________<br>> jifty-devel mailing list
<br>> <a href="mailto:jifty-devel@lists.jifty.org">jifty-devel@lists.jifty.org</a><br>> <a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel">http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
</a><br><br>_______________________________________________<br>jifty-devel mailing list<br><a href="mailto:jifty-devel@lists.jifty.org">jifty-devel@lists.jifty.org</a><br><a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel">
http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel</a><br></blockquote></div><br>