John,
Are you planning on methods for generating DDL from classes? Just curious.
Sean
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based
i've noticed that rose caches some information
example:
i try to insert a record, but the column length is to short
i update the column in the db
i try to insert a record, but the column length is to short- rose
has cached info ( i checked to see if it was because of
On 6/27/06, John Siracusa <[EMAIL PROTECTED]> wrote:
> The update() method has a changes_only parameter that instructs it to only
> update the columns whose values have been modified. I suppose I should add
> the same option to the insert() method (thus making it also valid on all
> calls to the s
On 6/29/06, Sean Davis <[EMAIL PROTECTED]> wrote:
> Are you planning on methods for generating DDL from classes? Just curious.
It's on my list, but it's low priority because most non-trivial db
schemas will contain constructs that cannot survive a round-trip
through RDBO. Column constraints or d
On Jun 29, 2006, at 2:12 PM, John Siracusa wrote:
> Should it be this?
>
> INSERT INTO mytable (name) VALUES ('foo');
>
> Or should it be this?
>
> INSERT INTO mytable (name, flag) VALUES ('foo', 1);
>
> They may seem identical, but now imagine if the default value in the
> "flag" column
On 6/29/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> i've noticed that rose caches some information
>
> example:
> i try to insert a record, but the column length is to short
> i update the column in the db
> i try to insert a record, but the column length is to sho
On Jun 29, 2006, at 2:27 PM, John Siracusa wrote:
> Well, you can't have it both ways. Either you want memory to be
> shared, in which case all the class setup and initialization can only
> happen once, in the Apache parent process, before the first fork, or
> you want everything to update "in r
this works, just checking to see if its the idiomatic way-- as the
docs didn't point to it...
basically:
a query in a manager for non-key fields...
results are stuffed into $results
check scalar @$ to see if there are results
i *think* @$results is the right way to hand
On 6/29/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> this works, just checking to see if its the idiomatic way-- as the
> docs didn't point to it...
>
> basically:
> a query in a manager for non-key fields...
> results are stuffed into $results
> check scalar @$ to see
