On May 25, 2006, at 8:35 PM, John Siracusa wrote:
Do you have any ideas about how to do so?
-John
Well it would depend on RoseDB supporting the dynamic variable
setting that you had contemplated earlier...
Since rosedb supports transactions, i'd imagine it would work easily
like this:
On 5/25/06 7:57 PM, Jonathan Vanasco wrote:
> i think emulating that behavior would
> be a real plus for rosedb mysql users.
Do you have any ideas about how to do so?
-John
---
All the advantages of Linux Managed Hosting--Without the Cost a
On May 25, 2006, at 7:16 PM, Jon Jensen wrote:
Yeah, sorry, I meant start of statement vs. wallclock time. Both
MySQL as of 5.0.13 and PostgreSQL since forever (AFAIK) give you a
way to get the wallclock time, but their now() pegs the time at a
different starting point.
Yep.
pg's now(
On Thu, 25 May 2006, Jonathan Vanasco wrote:
MySQL as of version 5.0.13 has two different times as well, now() and
sysdate(), for start of statement vs. start of transaction, as mentioned
here:
http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html
no, the MySQL has no transaction s
On May 25, 2006, at 6:27 PM, Jon Jensen wrote:
MySQL as of version 5.0.13 has two different times as well, now()
and sysdate(), for start of statement vs. start of transaction, as
mentioned here:
http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html
no, the MySQL has no transac
On Thu, 25 May 2006, Jonathan Vanasco wrote:
If you do create that, it would be really nice to implement it using postgres
type NOW() behavior for mysql
ie: mysql NOW() is whenever a NOW() is executed. postgres NOW() is the
transaction start time (though you can override with a standard func
On Thu, 2006-05-25 at 14:24 -0400, Guillermo Roditi wrote:
> is it really? because I couldn't figure it out. I dont want to use
> timestamps, and I dont know how to do it otherwise
Timestamps parse to DateTime objects as easily as datetime columns do.
This is what I use:
timestamp TIMESTAMP NOT NU
On 5/25/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
i need to pull this info quite a bit. would it be bad form to add it
into the a Manager derived class as such?
package MyApp::RoseDB::Object::UseraccountAsset::Manager;
use Rose::DB::Object::Manager;
our @ISA = qw(Rose::DB::Object::Ma
On May 25, 2006, at 1:30 PM, John Siracusa wrote:
This "dot-chaining" of relationship names in with_objects and
require_objects parameter values is demonstrated in the tutorial
section linked earlier. Search for the string "'vendor.region'" to
find the example.
kickass. thank you.
hopefull
On May 25, 2006, at 1:39 PM, John Siracusa wrote:
On 5/25/06, Guillermo Roditi <[EMAIL PROTECTED]> wrote:
I'd like to alter Rose::DB to be able to tabe a subref as a
default value
for a column in the table object classes so that upon insertion of
a new row
the default value can be dinamica
On 5/25/06, Perrin Harkins <[EMAIL PROTECTED]> wrote:
On Thu, 2006-05-25 at 13:26 -0400, Guillermo Roditi wrote:
Basically the promblem is that I want default for a column to be
NOW(). unfortunately that is getting insterted as -00-00 so my
guess is that it's getting screwed up in the place
On 5/25/06, Guillermo Roditi <[EMAIL PROTECTED]> wrote:
I am building a TODO manager, and I am having trouble grasping how i should
handle dependency relations within todo objects. here's a simplified layout
To_Dos
Fields: id (PK), title, due_date
To_Do_Dependencies
Fields: dependent_id (FK To_
On 5/25/06, Guillermo Roditi <[EMAIL PROTECTED]> wrote:
ahhh OK. so it's just mysql DBD::mysql that is dumb? that makes me feel
better. I can implement the subref functionality if you can give me a clue
as to where I should look for the code. theres so much inheritance going on
that I have a hard
is it really? because I couldn't figure it out. I dont want to use timestamps, and I dont know how to do it otherwise
ALTER TABLE `users`
CHANGE `touch_d` `touch_d`
DATETIME NOT NULL DEFAULT
NOW()
just kind of refused to workOn 5/25/06, Perrin Harkins <[EMAIL PROTECTED]> wrote
I'd like to alter Rose::DB to be able to tabe a subref as a default value for a column in the table object classes so that upon insertion of a new row the default value can be dinamically calculated. I looked in Metadata and Metadata::Column but I couldnt really locate myself very well. Is this som
On 5/25/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
i have the 2 packages below
Asset
AssetType
Asset is basically
name
id
type_id
where type_id is a fkey to another table
when i pull a record for Asset or join onto asset from another table,
i need t
On May 25, 2006, at 12:56 PM, Sean Davis wrote:
Not sure if this covers it, but did you look at this:
http://search.cpan.org/~jsiracusa/Rose-DB-Object-0.727/lib/Rose/DB/
Object/Tu
torial.pod#Auto-joins_and_other_Manager_features
Sean
yeah , i saw that but it only does it halfway
i should
On Thu, 2006-05-25 at 13:26 -0400, Guillermo Roditi wrote:
> Basically the promblem is that I want default for a column to be
> NOW(). unfortunately that is getting insterted as -00-00 so my
> guess is that it's getting screwed up in the placeholder stage, and I
> can't just do default => Date
Not sure if this covers it, but did you look at this:
http://search.cpan.org/~jsiracusa/Rose-DB-Object-0.727/lib/Rose/DB/Object/Tu
torial.pod#Auto-joins_and_other_Manager_features
Sean
On 5/25/06 12:46 PM, "Jonathan Vanasco" <[EMAIL PROTECTED]> wrote:
>
> i have the 2 packages below
> Asset
On 5/25/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
C->get_c(
query=> [
id => 1,
],
require_objects => [ 'B' , 'A' ],
);
where A isn't defined in C, but is a FKEY in class B
$cs = C->get_c(query => [ id => 1 ],
require
On 5/25/06, Guillermo Roditi <[EMAIL PROTECTED]> wrote:
I'd like to alter Rose::DB to be able to tabe a subref as a default value
for a column in the table object classes so that upon insertion of a new row
the default value can be dinamically calculated.
Yeah, I've been considering that featur
ahhh OK. so it's just mysql DBD::mysql that is dumb? that makes me feel better. I can implement the subref functionality if you can give me a clue as to where I should look for the code. theres so much inheritance going on that I have a hard time finding things around Rose::DB::Object sometimes
On
i have the 2 packages below
Asset
AssetType
Asset is basically
name
id
type_id
where type_id is a fkey to another table
when i pull a record for Asset or join onto asset from another table,
i need to get the asset_type_id name
sometimes i pull a record
I am building a TODO manager, and I am having trouble grasping how i should handle dependency relations within todo objects. here's a simplified layoutTo_DosFields: id (PK), title, due_date
PK: idTo_Do_DependenciesFields: dependent_id (FK To_Dos.id), dependee_id (FK To_Dos.id)PK: dependent_id, depe
24 matches
Mail list logo
