Exist in the market and everyone in the Web many solutions already developed that perform the same operation, some are complex script programming languages made rare for most people who work with Windows, I mean perls, python, ruby, bash , among others, it is also true that the vast majority of friendly applications that perform this task are proprietary, they have expensive plans, acquisition and use, but never too late to the computer world, when you do not see the exit only have to cling to what little light is left and wait for the spark is lit either by us or by the huge community of free software developers.

Migration Wizard is developed with the popular Java programming language, pose a very simple desktop interface that is guiding us for 7 short steps for the implementation of the Migration.

The first thing is to start the application from the group of tools that were installed with the suite EnterpriseDB.

The application starts and his first window indicates that you configure the data connection to MySQL server, which in this case is the source DB which we wish to migrate, including the necessary data is ask include:

• The server (host) where the server running MySQL, in my case, the server is running on the local machine (localhost), which means that the application Migration Wizard and MySQL are running on the same computer.
• The network port on the MySQL server connection is taking applications customers are interested in them do any transaction relating to any database, by default MySQL uses port 3306 to connect with customers who ask for the execution of an operation.
• The name of the source database (which you want to migrate to PostgreSQL), which in our case is the quejasyreclamos database, database I have previously created for an article on development of desktop applications with Java, the which this case ready.
• The user ID of the MySQL server that has privileges on the source database (quejasyreclamos in our case), I have placed the root user is the administrator who creates MySQL by default during the collation process, the user has privileges on all databases deployed on MySQL
• The password of the database Source, in my case I have not put password simply because I have not even put your root password

If we provide the data correctly, pressing the Next button will display the window on the second step, this step must tell the application which is the data connection to the target PostgreSQL server (on which will migrate from the base source data), data to be provided are:

• The server (host) where the server running PostgreSQL in my case, the server is running on the local machine (localhost), which means that the application Migration Wizard, the MySQL server and PostgreSQL server are running on the same computer.
• The network port to PostgreSQL server connections is taking applications customers are interested in them perform an operation related to any database, PostgreSQL uses the default port 5432 to connect with customers who ask for the execution of an operation.
• The name of the target database (which was implemented on the migration of the source database), which in our case is the quejasyreclamos database.
• The user ID the PostgreSQL server that has privileges on the source database (quejasyreclamos in our case), I placed the user postgres is the PostgreSQL administrator created by default during the collation process, the user has privileges on all databases implemented on PostgreSQL
• The password of the database origin, unlike MySQL, PostgreSQL requires that each user created on your system, you provide a password from the moment of its creation.

Pressing the button below Migration Wizard provides communication with the PostgreSQL server (if the host, port, username and password are correct) and asks you to let you use the quejasyreclamos database, the PostgreSQL server search inside this BD and not finding it sends the warning message, notifying you that has failed to CoNEXT to the database indicated that simply has not yet been created or was deleted, in my case, I made this way on purpose to show the notification message PostgreSQL sent to any customer who wishes to use a database that does not exist in their schemes.

The above problem is solved by creating the database schema quejasyreclamos as a data base within the PostgreSQL server, there are basically two ways to do this, one is using the postgres console client that comes with the installation of PostgreSQL , but being a script-based client console (Windows or DOS Bash GNU / Linux) is very cumbersome operability and user interface, the other way is to use any of the many graphical clients (desktop or web-like type ) operations developed for PostgreSQL server administration or DML (Data Manipulation Language, select, insert, update, delete, store_procedure and triggers) or DDL (Data Definition Language, create, alter, drop, grant, revoke , store_procedure and triggers) on their databases, these applications are much more comfortable, intuitive and easy-to-use console client application.

When selecting which of the available clients to work with PostgreSQL you use,you always lean towards the option provided by the supplier or developer of database server, as we are talking about PostgreSQL, its developer community has created almost Since its inception application called pgAdmin III, which in my opinion and evaluation, the best choice among all the reasons are many and we think the vast majority of them have no reason to explain.

To use pgAdmin III should be selected from the list of tools that are installed on the PostgreSQL menu.

Graphic graphic interface of this application is very intuitive, can be configured in virtually any language you only need to have basic concepts of databases and pgAdmin III provides all the functionality we needed to work with both the BD engine, which PostgreSQL is our case, as with their own databases it manages.

A complete database is composed of three parts:

• Databases: A collection of files called tables, structured by a storage standard that allows persistent operations (Insert, Modify, Delete and Find) in a very efficient and stable minimizadnos redundancy and inconsistency of information stored in those files. In this example the database is represented by quejasyreclamos
• The Database Engine: A system that defines the work rules, safety and handling of files (tables) and information, running or operation embodies the desire to perform in on stage, define which users can work on the basis data and privileges that they have no on them, among other things no less important. In this example the motor is represented by MySQL or PostgreDQL
• System Database Manager: The DBMS by its Spanish acronym, face towards the user (fontEnd), responsible for display users can perform operations on databases in a transparent, intuitive and secure, offers a Advanced layer of abstraction to the entire technology architecture upon which it is based and implemented database systems. In this example, the DBMS is represented by pgAdmin

There are some software that make up the engine and the DBMS in a single product, such as Microsoft Access and Open Oficce Base, while other systems are based upon an architecture called client-server, so that the Database Engine (plays Server role) can interact simultaneously with a large number DBMS (playing the role of client).

The first operation we must make the application once started pgAdmin III is connect to the Database Engine, normally they need data PosgreSQL server connection, such as IP or hostname of the computer where it is running the server, the user name you want to connect to the server and password, optionally the name of the database on which you want to work.

Established connection to the database server, what follows is to ask the dare of the SMB server to perform the operations we want to the extent of our privileges as a user, what concerns us now is creating a new database quejasyreclamos called PostgreSQL.

pgAdmin III shows an interface where you can specify the characteristics of this new database, such as name, type of encoding, the owner (admin user), restrictions, number of connections allowed simultaneously, where the value -1 is undefined .

In the SQL tab called us to lodge view the source code of SQL (Structured Query Language), which is the language in which you must speak to the Database Engine.

1. CREATE DATABASE quejasyreclamos
2. WITH ENCODING = ‘UTF’
3. CONNECTION LIMIT =- 1;

Saving changes to the DBMS builds the appropriate SQL statement based on our requests, are sent to the database engine to execute and deliver this the sovereign response the result of the operation, then the DBMS presents this information in a format quite understandable.

Created target database, we continue to step 3 of the migration process in this step we are asked to provide the format of the dates and type of migration is desired, which may be complete, only the structure of the bases data or only data from the database.

In step # 4 the migration wizard shows the databases found on database engine MySQL, which will allow us to choose the databases that will migrate to the target database PostgreSQL quejasyreclamos, if we choose more than a database, the migration process would export the whole scheme of databases into a single schema belonging to the target database, in other words, the target database will consist of all the elements that structure to each of the origin database.

In step # 5 to select the source database quejasyreclamos which is what concerns us in this paper, the migration wizard shows all the tables that make up this database, allowing us to select which of them will be those that will be part migration.

In step # 6 you can see specific details of the migration process

1. Source DATABASE connectivity info …
2. conn = jdbc: mysql: / / localhost: 3306 / quejasyreclamos
3. user = root
4. =****** password
5. DATABASE connectivity Target info …
6. conn = jdbc: edb: / / localhost: 5432 / quejasyreclamos
7. user = postgres
8. =****** password
9. Importing mysql schema …
10. Creating Schema … quejasyreclamos
11. Migrating Schema TABLES FOR quejasyreclamos ‘people’, ‘complaints’, ‘user’
12. Creating TABLES …
13. Creating TABLE: quejasyreclamos. People
14. Creating TABLE: quejasyreclamos. Complaints
15. Creating TABLE: quejasyreclamos. User
16. Created 3 TABLES.
17. Loading DATA IN TABLE 8 MB batches …
18. Loading TABLE: People …
19. Error Loading DATA INTO TABLE: People: Value ’0000-00-00 ‘can NOT Be Represented AS Java. Sql. Date
20. Loading TABLE: Complaints …
21. LOAD DATA TABLE Summary: Total Time (s): 0. 109 Total Rows: 0
22. Loading TABLE: user …
23. LOAD DATA TABLE Summary: Total Time (s): 0. 063 Total Rows: 0
24. Trying to reload TABLE: people-through bulk inserts WITH a batch size of 1000
25. Error Loading DATA INTO TABLE: people: NULL
26. LOAD DATA Summary: Total Time (sec): 0. 172 Total Rows: 0 Total Size (MB): 0. 0
27. Creating Constraint: PRIMARY
28. Creating Constraint: PRIMARY
29. Creating Constraint: PRIMARY
30. One or more schema objects Could not be imported DURING the migration process. Please review the migration output for more details.

Step # 7 finish the whole process and we see a reported message service or software support.

Now to see if everything went as we ask, we can return to the DBMS PgAdmin to see the outline of the new database engine quejasyreclamos within PostgreSQL.

Here you can see that the target database PostgreSQL quejasyreclamos pose the whole structure of the source database.

]]> http://master4webs.com/migrating-mysql-to-postgresql.html/feed 0 http://master4webs.com/getting-paid-on-the-web.html http://master4webs.com/getting-paid-on-the-web.html#comments Tue, 24 Aug 2010 04:38:58 +0000 admin http://master4webs.com/?p=4457 You still find it hard to believe, but after that recent trip to the mountains, something that you thought was dead has been reborn! The creative spark! Yes, it’s back, that tingly urge to craft, build, and endlessly modify, that very special feeling you thought had vanished for good after you failed “Art 101: Drawing and Sketching.” And now, after weeks locked in your studio — the light-deprived cube that your friends still refer to as your bedroom — you have created a small but appealing collection of objects de art (maybe sculpture, maybe music, maybe both!). Next step? Find a way to sell your fiery ingots of love.

With local galleries too narrow-minded (obviously!) to appreciate your work, you turn the Internet, really the best and most far-reaching distribution network out there. You take all the obvious steps: Build a site, take some photos, write descriptions, ZIP your files, encode your songs into MP3 and ready them for download. But what happens when somebody visits your site, likes what they see and hear, and wants to purchase one of your creations? Are you ready to dip your toe into the chilly waters of e-biz?

Whether you’re selling jewelry or you’re just a programmer out to make some spending money on the side, the transfer of funds from them to you is a big step. And that’s our topic for today — getting paid.

Of course, there are several different ways to receive funds online. Of course you can travel down the time-consuming-yet-intellectually-rewarding path of building your own shopping cart. Use Perl, ColdFusion, or transactional databases in MySQL, and you’re quite literally in business. But if you don’t have programming muscles to flex, let alone the time to build something yourself, why not set up shop with a Web storefront service? When moving currency from one party to another is involved, options are never hard to come by, and the time, money, and craftiness you need to implement them varies.

But what if you’re short on resources? Or you don’t have actual tangible items to sell? Maybe you want to accept donations for a free content service, collect payments for downloaded MP3s, or set up a payment system for a piece of software or Web-based application. Since no hard goods are exchanged — no shipping costs or taxes to calculate, no inventory being moved — simple cash payments may be the best answer.

If you do have actual trinkets to sell, hosting a third-party shopping cart on your site is also an option. Third-party shopping cart solutions are easy to put into action just by filling out a few forms and plugging in a credit card number (yours). However, since your users actually have go log in to a different and unfamiliar site when they want to purchase something, third-party shopping carts don’t provide your customers with a seamless shopping experience. Also, many of these systems require you to set up a merchant account. Merchant accounts, which we’ll look at in depth later, are tied to major financial institutions, so there are fees involved. The fees you pay for these all-inclusive systems will dramatically increase your overhead if you’re strictly small-scale. So if you’re still in mom-and-pop land, cash payments are the most economical and the easiest.

Cash payments on the Internet involve the transfer of funds from one person’s bank or credit card account to another person’s account. It’s the same basic idea as sending a check through the mail, except a Web payment is faster, easily trackable, and more secure. These types of low-level e-commerce, different from the more complex world of shopping carts and inventory management, are sometimes called “e-cash payments.” Several companies have developed payment systems that you can use either on a one-off basis, as a subscriber, or as a full-fledged credit merchant. Each service has its advantages and hang-ups, which is just what we’ll be looking at as we examine a variety of services in the pages that follow.

In addition to cash payment services, we’ll be cracking open e-wallet systems, as well as the aforementioned third-party shopping cart and merchant account services. I’ve rated all of these services based not only on their usability and coolness factors, but also on whether their sites clearly offered all the vital bits of info (security statements, fee schedules, and terms of use statements) — it’s difficult to trust a company that doesn’t provide all the facts right up front. Note that the list of services I chose to profile is by no means comprehensive. If you plan to use cash payments, I encourage you to follow up what you learn today with some research of your own before committing to a choice.

Let’s start with simple cash payments. There’s a company which I’m sure many of you are familiar with that handles millions of dollars in transactions per day. It’s called PayPal.

The QUERY tag is the main interface for executing arbitrary SQL on any table, regardless of the back-end.

QUERY synopsis

[query
	list="1"
	sql="SELECT * FROM products WHERE prod_group = 'Toys'"]

	<li>[sql-param description] - [price [sql-code]]</li>

[/query]

Step 1

QUERY is a container tag surrounding code that’s repeated for each row returned by the query, so it always has a closing tag.

Step 2

Passing list="1" tells Interchange that you’re expecting a “list”–or multiple rows, in other words. If you don”t pass this, the code surrounded by the QUERY tags won”t be executed. You need to pass this even if you”re only expecting one row in the results.

If you remember that “SELECT is a LIST” it won”t be a problem. But the QUERY tag is versatile enough that you can also run UPDATE and INSERT queries, and for these you can omit the list="1" parameter. You’ll still need a closing QUERY tag, though.

Step 3

The actual query is passed in the sql="SELECT..." parameter. From within here you can also use other Interchange tags, such as SCRATCH. Remember to quote anything, where necessary, like this:

[query
	list="1"
	sql="SELECT * FROM products WHERE prod_group = '[scratch prod_group]'"]

	... your code here ...

[/query]

Security warning: It’s tempting to pass user input in some form when creating queries. Writing prod_group='[CGI prod_group]' is a quick and easy way to start a search results page, but it can be exploited by a hacker, who could pass something like this:

	foo'; delete from products where sku != '

In this example, the ending quote and semicolon after foo closes the WHERE clause of the first query and then closes the query. The following query can then be executed, deleting all the products in your store. The code reading where sku != ' just makes sure there’s no syntax error that’d otherwise stop his malicious query from running.

To avoid accidents like this, you can screen incoming user data for quote marks and save the result in a scratch variable, like this:

[tmp prod_group][calc]
	my $group = $CGI->{prod_group};
	$group =~ s/'/''/g;
	return $group;
[/calc][/tmp]

The perl code here is substituting each single quote for a pair of single quotes (that’s not a double quote there, it’s two singles), which is how most SQL databases encode the quote character for use within strings passed to queries. With that in place, the hacker can’t get a malicious query to run, because he can’t break out of the first. In the worst case, the query would simply fail rather than delete all of your products.

You should always screen form-submitted data even if you’re passing it through hidden variables, or SELECT lists that constrain the input. None of these methods stop a hacker from contriving a GET or POST form submission with whatever he likes.

Step 4

The code to be run for each row of results is interpolated for SQL tags. The first useful tag is SQL-PARAM, which lets you pull any column from the results, even computed, virtual or renamed columns. For example:

[query
	list="1"
	sql="SELECT sku,description,
		date_format(entered,'%Y-%m-%d') as added,
		price + 10 as compare
		FROM products"]

	<li>[sql-param description] added [sql-param added]
		- [price [sql-code]] (compare to $[sql-param compare])</li>

[/query]

Advanced

ON-MATCH and NO-MATCH

Like with Interchange’s tags for summarizing search results, QUERY also understands the ON-MATCH and NO-MATCH tags to display something once when it finds rows, or doesn’t.

[query
	list="1"
	sql="SELECT * FROM products WHERE prod_group = '[scratch prod_group]'"]

	[on-match]
		<p>We found the following products for [scratch prod_group].</p>
		<ul>
	[/on-match]

	[list]
		<li>[sql-param description] - [price [sql-code]]</li>
	[/list]

	[on-match]
		</ul>
	[/on-match]

	[no-match]
		<p>Sorry, no matches for [scratch prod_group].</p>
	[/no-match]

[/query]

When you use the ON-MATCH or NO-MATCH tags, you imply the use of LIST as well. That’s because Interchange wouldn’t otherwise know what part of the code is meant to be repeated for each row.

In this example, there are two ON-MATCH blocks wrapped around the list to open and close a pair of HTML Unordered List tags. But you could also use them to open and close tables, paragraphs, or whatever.