The built-in function SYSDATE returns a DATE value containing the current date and time on your system. For example, UPDATE ACCOUNT SET LAST_MODIFIED = SYSDATE; updates the LAST_MODIFIED column to the current system time. select to_char(sysdate, 'MM-DD-YYYY HH24:MI:SS') N... prints the current date & time.

I'm not aware of any tool that reports runtime acquirement of permissions. Maybe such a tool or API exists, but I'm simply not aware of it. To the second part of your question, if you trust Google, no unlisted permissions can ever be acquired.

Thank you. Is there any way to show permissions which are actualy used by an app (should I say "active permissions") in a period of time and they may not be listed in the list of permissions when we install this app (mallware, etc.)? Thanks.

If I'm not wrong, Permissions are permissions provided by the app, while Requested Permissions are permissions used by the app.

Could you tell me please what are the differencies between the list Permissions and Requested Permissions? thanks.

This is handy for looking at compressed js files: http://jsbeautifier.org/ works pretty well.

Cause: Hibernate reverse engineering generated a column mapping like this: @Version @Column(name="VERSION", nullable=false... Fix: change the mapping to: @Column(name="VERSION", length=20) public Strin...

Redsocks is a transparent socks/proxy redirector. You use iptables to redirect TCP traffic to redsocks, redsocks will forward to upstream SOCKS4, SOCKS5 or HTTPS proxy server. Once set up, the redirection is system wide, so you don't have to set up proxy for each individual application. It is useful when you have to use a SOCKS or proxy server to make the connection but the application does not support proxy settings (for example, the Android browser). Linux/iptables, OpenBSD/pf and FreeBSD/ipfw are supported. Sample configuration file : base { log_debug = off; log_info = off; ... According to the project home page , redsocks is used by ProxyDroid to provide system-wide proxy on rooted Android devices.

You can use the runOrder parameter to control the test execution order for Maven surefire tests: <build> <plugins> <plugin> ... Other options are: Option Meaning alphabetical Alphabetical reversealphabetical Reverse Alphabetical random Randomized hourly alphabetical on even hours, reverse alphabetical on odd hours failedfirst Failed first will run tests that failed on previous run first, as well as new tests for this run. balanced Balanced is only relevant with parallel=classes, and will try to optimize the run-order of the tests to make all tests complete at the same time, reducing the overall execution time. filesystem This is the default. I guess this is the order returned by the file system: uncontrolled but deterministic.

Junit does not support specifying execution order of tests until 4.11. The methods were simply invoked in the order returned by the reflection API. So, the tests are executed in a unspecified but deterministic order, i.e., you have no control over the order of execution, but if you repeat the tests, they are run in the same sequence each time. For version 4.11, you can specify the order with the FixMethodOrder annotation: import org.junit.runners.MethodSorters; imp... From the release notes : Test execution order By design, JUnit does not specify the execution order of test method invocations. Until now, the methods were simply invoked in the order returned by the reflection API. However, using the JVM order is unwise since the Java platform does not specify...