There are no problems in mixing both emgines
however one should pay attention to the following
<<< // from manual
for best results, you should not mix different storage engines within a transaction with autocommit disabled.
>>>
I am in a situation where I need to implement InnoDB transaction capability.
But this will call for ALTER a few tables of a DB previously set exclusively with MyISAM table engine.
Is there any problem to foresee while operating a DB with a mixed table engine combo made of MyISAM & InnoDB?
Yes you are correct, I use MySQL and will have to alter some tables from myISAM to InnoDB
I might post to MySQL but it will spread out the thread
for now the real simple last question becomes:
Is there any problem to foresee while operating a DB with a mixed table engine combo made of MyISAM &...
In a member driven environment I offer to the members the opportunity to delete part of or their whole account
The process is quite involving
Deleting/updating/inserting in six tables
Opening and deleting from a video repository
Opening and deleting from an img gallery
As is it works fine
But...
Your query ex made me think and I made it working, thanks.
$result2 = $db->query("
SELECT COUNT( aaaa ) AS cnt, COUNT( bbbb ) AS cnt2
FROM xxxxx
WHERE productId = '6'
AND customer_id = '$id'
");
$check=$db->num_rows($result2);
if($check >0 )
while ($row=$db->fetch_array($result2) )
{
{...
Thank you, my biggest problem is that I may not use (*)
reason is (Sorry, I should have precised)
I need actually to select and count two different cols from the table with the same condition (productId and customer_id)
then I will compare which col/rows is equal or non equal to the other one
so...
The following should work (I suppose) but is resulting in empty result
$result2 = $db->query("
SELECT productId
FROM xxxxx
WHERE productId = '6'
AND customer_id = '$id'
");
$check=$db->num_rows($result2);
if($check >0 )
{
$check1=$result2['COUNT(productId)'];
echo"check1: $check1<P>";
}
I found my error
The rest of the script is under the influence of
a quantity that I got from $aaa=$_FILES[‘image_file’]
which was reading all components of the file (5) although I was passing only one img
Not a good idea to do as I did!
Be sure (if testing for a quantity) to check for only a...
On a few hundred of lines I call a foreach quite a few times
(Checking img file)
It works fine in a multiple files environment
But if the user enters only one element then the foreach runs one too many time and adds an empty element
How could I go around that problem, do I have to set a switch...
What comes in mind first is:
Is the server setup to allow for outside communications, or does not accept mail from the IP you try to access.
Are you running fedora? if so
add to the Kernel command line selinux=0
BTW is fsockopen enabled on your account?
I did a search and that pretty much...
Try this, using an alternate port
includes/phpmailer/class.smtp.php -
set var $SMTP_PORT = 2525;
includes/phpmailer/class.phpmailer.php -
set var $Port =2525;
Not feeling too bright!
it has to be obvious but...
I am trying as per the code example to populate a DD box from an array
the box picks up the correct number but each value reads "array" instead of the array value
if ($quantity==1) { $q=array(1=>"1"); };
if ($quantity==2) { $q=array(1=>"1"...
I do not see it as cart
A) display sections and sub sections, have an icon that shows something is needed it that section or sub section (if too many pages use pagination) or even if is really really returning too many items then only show the desired items
Although I like the idea of showing...
Thanks, I did not figure that out
so I tested with
$reg_time= date("G-i-s-m-d-Y",$regTime);
and ketp the zeros in
$timestamp= mktime(0,0,0,10,9,2007);
Next
added G-i-s value to $timestamp
The final result is now as expected.
However it sounds quite a long procedure to reach the desired result...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.