Just market the chips as "Academic Editions" and sell them to universities at a discount. Then we'll see what Professor Pointyhead says when defective chips end up on his desktop, in his nic, in his cell phone, or in the LCD projector that he uses to teach a class.
http://sql-info.de/ http://sql-info.de/mysql/gotc has.html [MySQL gotchas] http://sql-info.de/postgresql/postgres-g otchas.htm l [PostgreSQL gotchas]
The above site has a list of problems and SQL incompatibilities for both PostgreSQL and MySQL. The list for MySQL is quite long, but just looking through the first five examples on the first page will give you a feel for the problems.
A primary issue is data integrity. Some of the examples in the "MySQL gotchas" show flawed input data being modified by the system when an error should have been returned. That means the resulting data set may not contain the information you expect it to contain.
One issue with executing queries on a database is knowing when you are getting the correct result. If a query returns 100 records, then it looks like that must be the correct result. But if the query should have returned 150 records, but didn't because the system silently added or modified input data in order to accept some flawed input, then data integrity is lost; you can't trust your database.
If you're interested in finding out more about database systems, "A First Course in Database Systems" by Ullman and Widom is a pretty good book that is used in college courses. I kept my copy.
Re:hah I'm like that
on
Cube Farm
·
· Score: 2, Insightful
You claim you were a sysadmin, but you can't understand why you are not allowed to install any software you want on your company-owned computer? You are angry that you are not allowed to run unauthorized software from a USB key? Maybe these issues are the reason you are not in your previous all-powerful job.
You claim that the company that provides your software charges hundreds of dollars per line of source for indemnification. Well, for that price, the cost of Windows XP indemnification would probably exceed the cost of litigation resulting from the use of Windows XP.
Why is it necessary to take a beginners course in Java before installing WSAD? Perhaps your job as a Technical Analyst does not require such a comprehensive programming environment, and the sysadmins require you to justify the cost of a license and to prove you can actually use a part of the functionality.
There are some resources on the Microsoft site that may be of interest to you. Make sure no spaces were inserted into the urls.
On the Microsoft Developers Network:
The "Unix Application Migration Guide" can be read online and is available as a PDF. The guide is about 2 years old, but it is the result of many consultants refining the process.
http://msdn.microsoft.com/library/?url=/library/ en -us/dnucmg/html/ucmglp.asp?frame=true
Chapter 1 Introduction Chapter 2 UNIX and Windows Compared Chapter 3 The Migration process Chapter 4 Assessment and Analysis Chapter 5 Planning the Migration Chapter 6 UNIX and Windows Interoperability Chapter 7 Creating the Development Environment Chapter 8 Preparing for Migration Chapter 9 Win32 Code Conversion Chapter 10 Interix Code Conversion Chapter 11 Migrating the User Interface Chapter 12 Testing and Quality Assurance Chapter 13 Creating the Live Environment Chapter 14 Migrating Fortran Chapter 15 Roadmap for Future Migrations
On Microsoft Technet:
Windows Services for UNIX provides an environment to integrate your Windows machines into your UNIX environment.
If you want to send a repository, or a portion of a repository, for use elsewhere, just dump the data using the "svnadmin dump" command. The recipient can put the data into a new repository with the "svnadmin load" command.
The existence of a repository, or a database storage component in the repository, does not relieve you of the necessity of making backups of the repository.
I used to work at a remote location for a defense contractor and one of the home office guys was publicly terminated. He went to work and his supervisor and a couple of security guards came to his cubicle and ordered him to clear out his desk and leave within fifteen minutes. This was a layoff, not a firing. The security guards stayed to ensure the former employee complied. A friend of the terminated employee (the guy who spread the story to all the remote locations) was so peeved that he began to follow the supervisor around and document everything the supervisor did, hoping to get some dirt that would result in the supervisor being fired. The supervisor told the disgruntled friend that a letter was going into his personnel file about all the company time he wasted sneaking around behind the supervisor with a notepad. The disgruntled friend took a swing at the supervisor and got fired for cause.
Slashdot Mirror
There is a simple solution.
Just market the chips as "Academic Editions" and sell them to universities at a discount. Then we'll see what Professor Pointyhead says when defective chips end up on his desktop, in his nic, in his cell phone, or in the LCD projector that he uses to teach a class.
Maybe he won't notice.
http://sql-info.de/c has.html [MySQL gotchas]g otchas.htm l [PostgreSQL gotchas]
http://sql-info.de/mysql/got
http://sql-info.de/postgresql/postgres-
The above site has a list of problems and SQL incompatibilities for both PostgreSQL and MySQL. The list for MySQL is quite long, but just looking through the first five examples on the first page will give you a feel for the problems.
A primary issue is data integrity. Some of the examples in the "MySQL gotchas" show flawed input data being modified by the system when an error should have been returned. That means the resulting data set may not contain the information you expect it to contain.
One issue with executing queries on a database is knowing when you are getting the correct result. If a query returns 100 records, then it looks like that must be the correct result. But if the query should have returned 150 records, but didn't because the system silently added or modified input data in order to accept some flawed input, then data integrity is lost; you can't trust your database.
If you're interested in finding out more about database systems, "A First Course in Database Systems" by Ullman and Widom is a pretty good book that is used in college courses. I kept my copy.
You claim you were a sysadmin, but you can't understand why you are not allowed to install any software you want on your company-owned computer? You are angry that you are not allowed to run unauthorized software from a USB key? Maybe these issues are the reason you are not in your previous all-powerful job.
You claim that the company that provides your software charges hundreds of dollars per line of source for indemnification. Well, for that price, the cost of Windows XP indemnification would probably exceed the cost of litigation resulting from the use of Windows XP.
Why is it necessary to take a beginners course in Java before installing WSAD? Perhaps your job as a Technical Analyst does not require such a comprehensive programming environment, and the sysadmins require you to justify the cost of a license and to prove you can actually use a part of the functionality.
"... you're allowing someone else to determine just how 'stable' it is ..."
Yeah, you're allowing the project developers to determine the stability of their project code. Beta? Gamma? What do they know anyway?
There are some resources on the Microsoft site that may be of interest to you. Make sure no spaces were inserted into the urls.
/ en -us/dnucmg/html/ucmglp.asp?frame=true
p
On the Microsoft Developers Network:
The "Unix Application Migration Guide" can be read online and is available as a PDF.
The guide is about 2 years old, but it is the result of many consultants refining the process.
http://msdn.microsoft.com/library/?url=/library
Chapter 1 Introduction
Chapter 2 UNIX and Windows Compared
Chapter 3 The Migration process
Chapter 4 Assessment and Analysis
Chapter 5 Planning the Migration
Chapter 6 UNIX and Windows Interoperability
Chapter 7 Creating the Development Environment
Chapter 8 Preparing for Migration
Chapter 9 Win32 Code Conversion
Chapter 10 Interix Code Conversion
Chapter 11 Migrating the User Interface
Chapter 12 Testing and Quality Assurance
Chapter 13 Creating the Live Environment
Chapter 14 Migrating Fortran
Chapter 15 Roadmap for Future Migrations
On Microsoft Technet:
Windows Services for UNIX provides an environment to integrate your Windows machines into your UNIX environment.
http://www.microsoft.com/windows/sfu/default.as
I hope this stuff is helpful.
If you want to send a repository, or a portion of a repository, for use elsewhere, just dump the data using the "svnadmin dump" command. The recipient can put the data into a new repository with the "svnadmin load" command.
The existence of a repository, or a database storage component in the repository, does not relieve you of the necessity of making backups of the repository.
I used to work at a remote location for a defense contractor and one of the home office guys was publicly terminated. He went to work and his supervisor and a couple of security guards came to his cubicle and ordered him to clear out his desk and leave within fifteen minutes. This was a layoff, not a firing. The security guards stayed to ensure the former employee complied. A friend of the terminated employee (the guy who spread the story to all the remote locations) was so peeved that he began to follow the supervisor around and document everything the supervisor did, hoping to get some dirt that would result in the supervisor being fired. The supervisor told the disgruntled friend that a letter was going into his personnel file about all the company time he wasted sneaking around behind the supervisor with a notepad. The disgruntled friend took a swing at the supervisor and got fired for cause.
Any other Defense Contractors out there?