TIPS: SQLite: Python: How to get the details of a table


There are two ways you can achieve it.
1.
cursor.execute(“PRAGMA table_info(tablename)”)
print cursor.fetchall()

2.
sql = sqlite3.connect(self.cFile)
c = sql.cursor()
query = “select * from preferences”
c.execute(query)
col = [tuple[0] for tuple in c.description]
print col

Note:
cur.description returns a tuple of information about each table. The entire tuple is : (name, type_code, display_size, internal_size, precision, scale, null_ok)

Advertisements

QA: MSI Interview: What is the difference between installations using ALLUSERS=””, ALLUSERS=1 and ALLUSERS=2 option?


Q: What is the difference between installations using ALLUSERS=””, ALLUSERS=1 and ALLUSERS=2 option?

ANS:

  1. ALLUSERS=””: It specifies per-user installation context
  2. ALLUSERS=1: It specifies per-machine installation context
  3. ALLUSERS=2: It enables the system to define the values of ALLUSERS, and in turn the installation context, dependent upon the user’s privileges and the version of Windows
  1. Windows 7: Uses the MSIINSTALLPERUSER property to specify the installation context.

i. MSIINSTALLPERUSER ="": Per-Machine installation.

ii. MSIINSTALLPERUSER =1: Per-User installation

  1. Windows Vista: Windows Installer complies with User Account Control (UAC). If the user has user access privileges, and ALLUSERS=2, the installer performs a per-machine installation only if Admin credentials are provided to the UAC dialog box. If UAC is enabled and the correct Admin credentials are not provided, the installation fails with an error stating that administrator privileges are required. If UAC is disabled by the registry key, group policy, or the control panel, the UAC dialog box is not displayed and the installation fails with an error stating that administrator privileges are required.
  2. Windows XP: Set Windows Installer performs a per-user installation if the user has user access privileges.
  3. Windows 2000: Windows Installer performs a per-machine installation if the user has administrative access privileges on the computer. If the user does not have administrative access privileges, Windows Installer resets the value of the ALLUSERS property to an empty string ("") and performs a per-user installation.

QA: MSI Interview : What are the ADDLOCAL and ADDSOURCE properties?


Q: What are the ADDLOCAL and ADDSOURCE properties?

Ans:

  1. ADDLOCAL:

It is the property which contains the list of features, delimited by commas (,), which are to be installed locally. These features must be present in the Feature column of the Feature Table.

  1. ADDSOURCE:

It is the property which contains the list of features, delimited by commas (,), which are to be installed to run from the Source. These features must be present in the Feature column of the Feature Table.

QA: MSI Interview: Explain the difference between Property and PROPERTY


Q: Explain the difference between Property and PROPERTY

ANS:

  1. Public Property:

Public properties can be changed anytime by a user, system or admin on the command line while installing, by applying a transform or by interacting with the authored user interface (Installation Interface)

They are always in upper case

  1. Private Property:

The installer uses then internally and their values are initialized in the installation database (msi) or set by the values determined by the OS.

Private property names must always include lowercase letters. (Thanks Alek for correcting)

Few annoying issues with App-V


Few issues or blocks which I found with App-V are as follows:

  1. If two application (say excel 2007 & Excel 2002) have same file type associations (say .xls) then the last one cached gets the file type associations.
  2. If any office application (say excel.exe) is locally installed and is currently running and is in focus then virtual excel will not launch even if the file type association is set for it.