Daniel Convissor wrote:
PHP code. Most importantly, if you name everything "id," then you have
to explicitly spell out your JOIN statements in an ON clause
SELECT product_name, vendor_name
FROM product
JOIN vendor ON (vendor.id = product.vendor_id)
When it's so much easier to take advantage o
Folks:
Folks:
On Mon, Aug 31, 2009 at 06:06:22PM -0700, Kristina D. H. Anderson wrote:
> For instance imagine pulling out the contents of ten tables through ten
> queries in one script, and all the ID fields are named, id.
So true. Using "id" as the primary keys means you need to make aliases
Bev,
Essentially the thinking is that whenever you're processing code that
involves a lot of tables or a lot of queries (and returned results),
you end up with a bucketload of things named 'id' to handle.
For instance imagine pulling out the contents of ten tables through ten
queries in one
When i do $myOrder->save();
it seems to be taking all the values that I just set and setting them back.
- Original Message -
From: "Chuck Reeves"
To: "NYPHP Talk"
Sent: Monday, August 31, 2009 3:49:35 PM
Subject: Re: [nyphp-talk] Magento Commerce Experience
be sure to call the
>
> Yeah what exactlly you wanna know?
>
> Mona Borham
> Web Developer
>
>
>
> On Mon, Aug 31, 2009 at 10:49 PM, Chuck Reeves wrote:
>
>> be sure to call the save method after you call the set.
>>
>> ex
>> $myOrder= Mage::getModel('sales/order');
>> $myOrder->load($orderId);
>> $myOrder->setSta
Yeah what exactlly you wanna know?
Mona Borham
Web Developer
On Mon, Aug 31, 2009 at 10:49 PM, Chuck Reeves wrote:
> be sure to call the save method after you call the set.
>
> ex
> $myOrder= Mage::getModel('sales/order');
> $myOrder->load($orderId);
> $myOrder->setState(Mage_Sales_Model_Or
be sure to call the save method after you call the set.
ex
$myOrder= Mage::getModel('sales/order');
$myOrder->load($orderId);
$myOrder->setState(Mage_Sales_Model_Order::STATE_PROCESSING, true, 'Order
Processing Started '); //any other set method will work here
$myOrder->save();
Thank You
Chuc
Yes I've already developed a module that provides alternate code for built-in
code...but the problem I am having is that I am trying to update the totals,
grand totals, tax totals, for orders and quotes but it seems like i set the
value inside of one object..then inside another object I try to g
It has a steep learning curve and can be very slow at times. That
considered, it is designed in an incredibly modular manner, so you can
pretty much provide an alternate module for any built-in code, so,
it's highly customizable. It has one of the organized code bases I've
ever seen.
- jake
On Mo
Does anyone on the list have experience with Magento Commerce
http://www.magentocommerce.com
___
New York PHP User Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org/show_participation.php
Hans Zaunere wrote:
Mine does - they aren't "global" but scoped only for that template. When an
object is pushed in, it's adapted/wrapped with an object that is designed
specifically for output in whatever type of template I'm dealing with.
That could work well, but I do have some fear
Late to this party, but something I find useful wrt to NULL is that php's
isset() will return FALSE if a variable is NULL. It would return TRUE if the
same variable was set to 0 or empty string.
--Mike H
PS sorry for the top post my blackberry is being a PITA
--Original Message--
From:
> > Yeah something like this could be handy, certainly. I typically
push/adapt
> > an object into the template which is property overloaded. Then
something
> > like:
> >
> > FirstName?>
>
> I'm afraid that this is getting us back to magic_quotes_gpc:
Negative - magic_* is global type behavior t
Hans Zaunere wrote:
Yeah something like this could be handy, certainly. I typically push/adapt
an object into the template which is property overloaded. Then something
like:
FirstName?>
I'm afraid that this is getting us back to magic_quotes_gpc:
because now I might want to write
$
Kristina D. H. Anderson wrote:
>
> ...and also to never use just "id" for the primary key field name.
>
Hi Kristina,
I'm probably going OT when I shouldn't, but I'm so glad you mentioned
that because I was just wondering about it yesterday. I started out
using "id" because it was easy when I n
I was trained from the get-go back when I was using Access and SQL
Server in the 90s to never, ever use reserved words for table or field
names...and also to never use just "id" for the primary key field name.
I'm wondering why both phpMyAdmin and a number of the boilerplate PHP5
frameworks' da
Good morning,
> > So Bev, you taking the lead?
> >
> > Leam
>
> Hi Leam,
>
> I'm not sure. I sent an email to Hans saying I'd be happy to help in
> whatever capacity I can, so I'm waiting hear back from him.
Sorry, I need to call roto router on my inbox...
> Do you want to help too? If so, I t
Leam Hall wrote:
> So Bev, you taking the lead?
>
> Leam
Hi Leam,
I'm not sure. I sent an email to Hans saying I'd be happy to help in
whatever capacity I can, so I'm waiting hear back from him.
Do you want to help too? If so, I think we're supposed to discuss things
over on the Org list.
Bev
So Bev, you taking the lead?
Leam
li...@nopersonal.info wrote:
Hans, this sounds great. Your other email just came in, so I'm going to
sign up for the Org list and then I'll read through what you sent.
Regards,
Bev
___
New York PHP User Group Commu
19 matches
Mail list logo
