| From: | Sandeep Srinivasa <sss(at)clearsenses(dot)com> |
|---|---|
| To: | Allan Kamau <kamauallan(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: MySQL versus Postgres |
| Date: | 2010-08-09 06:54:11 |
| Message-ID: | AANLkTikY8YTHno4R-uGoAyp5POF3shjAOwbzBtqemEBt@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Aug 9, 2010 at 12:15 PM, Allan Kamau <kamauallan(at)gmail(dot)com> wrote:
>
> There may be worry of "copy and paste" without proper understanding of
> the code and concepts but this may be mitigated IMHO by fact that it
> seems unlikely that when presented with a case to solve, simple "copy
> and paste" of several commands (in the right sequence) will happen and
> correctly solve the problem at hand without appreciation of what these
> commands and statements do. Also more often or not the "copy and
> paste" will only work on specific schema definitions and data used in
> the example, therefore reconstruction (hence understanding) of these
> commands is neccessary.
The way I see it - for those who want to truly learn, there is the
documentation. For those who dont, there are ORMs.
For the rest of us, still floundering in MySQL land, please build a bridge.
-Sandeep
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2010-08-09 07:33:09 | Re: MySQL versus Postgres |
| Previous Message | Allan Kamau | 2010-08-09 06:45:28 | Re: MySQL versus Postgres |