I have a database that is constantly growing, so I must take great care of these records.

I was looking on the internet and Oracle Corporation (owner of MySQL since 2010) provides a paid product, MySQL Enterprise Backup , to perform this type of backup with one command, mysqlbackups.

An example of use:

mysqlbackup --backup-image=/backups/sales.mbi --backup-dir=/backup-tmp backup-to-image

With this tool there is a way to perform incremental backup and perform differential backup.

My question basically is: How to perform an incremental or differential backup with basic MySQL commands?

Reviewing some JavaScript codes, I find a peculiarity, sometimes it is used preventDefault()but in others a return false;, for example:

function with return false;:

function() {
  return false;
}

function with preventDefault();:

function(e) {
    e.preventDefault();
}

A more specific example would be the following:

$('a').click(function () {
    return false;
});
//----------------------------
$('a').click(function (e) {
    e.preventDefault();
});

Update

Álvaro 's answer has clarified some doubts and has generated others, for example, he mentions:

In jQuery, return falseit's equivalent to doing preventDefaultandstopPropagation

Which with your examples is quite understandable, but continuing with my research, I see two more events that work with similar purposes , the first is stopPropagationand the other is stopImmediatePropagation. stopPropagationSo far I have understood it, but what about del stopImmediatePropagation?

The examples that have been answered so far have helped me a lot to understand how it works, however, now it is not clear to me when it is feasible to use stopImmediatePropagation.

For example, focusing on jQuery, what would be the result of executing the following code?

$('a').click(function (e) {
    e.preventDefault();
    e.stopPropagation();
    e.stopImmediatePropagation();
});

Given the above, I have a few questions:

1. What is the difference between use preventDefault()and return false;? ( Doubt resolved )
2. When to use one or the other? ( Doubt resolved )
3. Is it preferable to lean towards one of the two mentioned? ( Doubt resolved )
4. What is it for stopImmediatePropagationand what advantages would I have when using it?
5. What difference is there when using stopPropagationagainst stopImmediatePropagationor using them together?

Yesterday(February 6, 2017) I was bombarded with emails from Google Play Support , saying that my apps had privacy policy issues and if not changed they would be hidden.

Their solution is the following:

Add a privacy policy to the Play Store listing page

1. Access the Google Play Developer Console .
2. Select an app.
3. Select the Play Store listing.
4. In the "Privacy Policy" section, enter the URL where you have the online privacy policy hosted.
5. Select Save Draft (new apps) or Send Update (current apps).

So far I don't know how to generate the url with the privacy policies, so I leave two questions : should I create a website and attach the privacy policies to it? Do they have to have a special format?

But then I checked my privacy tab and I found the following alert:

Your APK requests the following permissions: android.permission.GET_ACCOUNTS. Apps that use these permissions in an APK must have a privacy policy configured.

I don't use this permission, but I know that using the GCM library com.google.android.gms:play-services-gcm:8.3.0 would be calling the android.permission.GET_ACCOUNTS permission. I think I already have "control" (or so I hope) this problem, by adding the following line in my manifest:

<uses-permission android:name="android.permission.GET_ACCOUNTS" tools:node="remove" />

Now, I leave the third and fourth question: If I add this line in my manifest , will the problem be solved in the Play Store? Will it affect how notifications work? (in the tests that I have carried out the notifications arrive without problem)

----------

Since things are slow, I EDIT to answer myself only.

The issue of removing permission using

<uses-permission android:name="android.permission.GET_ACCOUNTS" tools:node="remove" />

In the GCM documentation it is indicated that it is used for:

For devices prior to 4.0.4, GCM communication requires users to set up their Google account on their mobile devices, but is not a requirement on devices running Android 4.0.4 or higher (API Level 15 or higher). .

Removing the permission would cause problems in versions lower than API 15, in my case minSdkVersion 11I defined then, it should not remove the permission and I am obliged to link the privacy policy... Unfortunately the permission will be displayed on devices equal to or greater than API 15 , which do not need permission. Is there a way to remove the permission only on devices higher than API 15?

Read more about this topic in this thread

Summary of Questions:

1. Is there a way to remove the permission only for devices higher than API 15?, that is, a different manifest per Android version
2. Should I create a website and attach the privacy policies to it?
3. Do they have to have a special format?

I am informing myself with the functions to interact with the user. I'm with the basics: raw_input()e input(). I have read that it input()only takes integer data, that it does not accept strings, and that for this we use raw_input().

The problem is that if I store a string in a variable with input()if it accepts it and recognizes it. But if I try to do the same with raw_input()it gives me the following error:

Traceback (most recent call last):
  File "lllll.py", line 9, in <module>
    raw_input()
NameError: name 'raw_input' is not defined

I work with Python 3.5.2

We consider that the variable $foocontains a string with value hello world . My question is: how could one check if it $foocontains the word world and throw a echo?

$foo = 'Hola mundo';

if($foo contiene 'mundo') {
  echo 'True';
}