| Ссылки |
|---|
 Keylogger Software: Elite keyloger by Widestep Keyloggers Software
|
| Ссылки |
|---|
|
|
Новости, последняя информация о open source...
Perl, PHP, другие языки программирования и программное обеспечение с открытым исходным кодом... поиск работы в этой сфере... всему этому посвящен наш сайт
Добро пожаловать!!!
|
|
|
|---|
 As tweeted by Fabien Potencier, symfony2 now has a “translations” page on their site. If you read and write English and another language, they want you! |
|
| |
|
|---|
 The new edition of this best-selling guide to Ubuntu for beginners covers Ubuntu 10.04, Lucid Lynx. Grant tackles topics likely to be of interest to the average desktop user such as installing software; connecting to the Internet; working with flash drives, printers, and scanners; burning CDs and DVDs; playing audio and video; using iPods; customization; and even a bit of the command line. Based on reader feedback, this edition includes even more screenshots and visuals; more troubleshooting help; more specific tips and tricks; and a bit more technical stuff, in plain English of course. |
|
| |
|
|---|
| Zend Technologies Launches Unlimited Subscription Model for Businesses Using PHP; Signs Major Enterprise Customers in U.S., Europe |
|
| |
|
|---|
 File this under "you learn something new every day." I came across this little tidbit while browsing the source code for psql: you can have a per-version .psqlrc file which will be executed only by the psql associated with that major version. Just name the file .psqlrc-$version, substituting the major version for the $version token. So for PostgreSQL 8.4.4, it would look for a file named .psqlrc-8.4.4 in your $HOME directory. It's worth noting that the version-specific .psqlrc file requires the full minor version, so you cannot currently define (say) an 8.4-only version which applies to all 8.4 psqls. I don't know if this feature gets enough mileage to make said modification worth it, but it would be easy enough to just use a symlink from the .psqlrc-$majorversion to the specific .psqlrc file with minor version. This seems of most interest to developers, who may simultaneously run many versions of psql which may have incompatible settings, but also could come in handy to regular users as well. |
|
| |
|
|---|
Flymake is an on-the-fly syntax checker for Emacs. Here is how you can use it for editing the PostgreSQL source code. Add this to your src/Makefile.custom:
check-syntax:
$(COMPILE.c) -fsyntax-only $(CHK_SOURCES) Then you can activate the flymake minor mode either manually using M-x flymake-mode, or by adding it to your Emacs customization for PostgreSQL. I use:
(defun pgsql-c-mode ()
"C mode adjusted for PostgreSQL project"
(interactive)
(c-mode)
(flymake-mode)
; .. and the rest ...
) Here is a screenshot:
Notice the marked line with the syntax error and the tooltip/popup with the error message, which appears when the mouse hovers over the marked line.
Note, however, that since activating flymake will essentially cause a compiler to be running continuously in the background, this is not what you want to use when hacking PostgreSQL on the road. ;-) |
|
| |
|
|---|
In a new post to his blog today Gonzalo Ayuso offers some tips for those out there wanting to cluster their PHP applications effectively. |
|
| |
|
|---|
| I expected feedback from the community on FOSSExperts. I did not expect feedback with such immediacy. All the feedback I have received so far is positive. Which is a great feeling. Here are the key points that are coming back. How do deal with disagreement about the deliverable: This is an interesting one. I wanted to keep FOSSExperts simple. That is why the deliverable on the ALTER TABLE project is simple, committed to PostgreSQL Core. That may not work in all circumstances. So I am considering one of two options. The first option is courtesy of Josh Berkus. The idea would be to have a board of people that determine whether or not the deliverable has been met. This has merit because you have a panel of experts that make the determination. It can make the review process painless but is also takes the power out of both the funders and developers. The second one is to take a vote. It would work something like this. - Developer states project is complete and demonstrates completeness based on the deliverable.
- Every person who ...read more...
|
|
| |
|
|---|
 The end of the road for the Nexus One (LWN) -- The pessimistic among us can be forgiven for concluding that the battle for open handsets is being lost. The carriers determine which devices will be successful in the market, and they have absolutely no interest in openness. Customers are irresistibly drawn to heavily advertised, shiny devices with low...  |
|
| |
|
|---|
| About a month ago my good friend Lorna Mitchell put out a call for stories on how working with Open Source has influenced people's careers. Given that a lot of my recent career has been driven by my involvement in Open Source, I shared my story with Lorna. But I also wanted to share some of my story with everyone. So here is my story and opinion on how Open Source can influence your career in a positive way. |
|
| |
|
|---|
By far the most common issues we see reported with the "one-click" PostgreSQL installers that we build here at EnterpriseDB are password related. In this post I'll explain what the passwords are, why we need them, and how to reset them.
Superuser Password
The Superuser Password is used by Postgres to secure the built-in "postgres" superuser account in the database itself. This is the only account found in a fresh installation. The password is setup during the initial installation of the database server, and may be changed at any point in the future using pgAdmin, or by issuing an SQL query such as:
ALTER USER postgres WITH PASSWORD 'VeryVerySecret';
The superuser password is not required to upgrade Postgres to a newer version, however it will be required if you install certain StackBuilder modules, such as PostGIS or any of the PHP applications that are available. The password is required for these installers because they connect to the database server and create databases and other objects required to ...read more... |
|
| |
|
|---|
| On 25th Robert Haas committed patch which adds first of ‘CREATE IF NOT EXISTS’ commands: Log Message: ----------- CREATE TABLE IF NOT EXISTS. Reviewed by Bernd Helmle. Example is of course trivial: $ create table if not exists tesit (x text); CREATE TABLE $ create table if not exists tesit (x text); NOTICE: [...] |
|
| |
|
|---|
| July was a month of talks and travel, including speaking at OSCON and user group talks to DCPHP and PDXPHP. For those who saw the “Micro Optimize This!” talk, you can download the slides here. For those looking for the “Five Tips To Make Good Object Oriented Code Better” slides, those are available here. |
|
| |
|
|---|
| Sometimes when you're doing something in SQL, you find yourself doing something repetitive, which naturally lends itself to the desire to abstract out the boring parts. This pattern is often prevalent when doing maintenance-related tasks such as creating or otherwise modifying DDL in a systematic kind of way. If you've ever thought, "Hey, I could write a query to handle this," then you're probably looking for dynamic SQL. The standard approach to using dynamic SQL in PostgreSQL is plpgsql's EXECUTE function, which takes a text argument as the SQL statement to execute. One technique fairly well-known on the #postgresql IRC channel is to create a function which essentially wraps the EXECUTE statement, commonly known as exec(). Here is the definition of exec():
CREATE FUNCTION exec(text) RETURNS text AS $$ BEGIN EXECUTE $1; RETURN $1; END $$ LANGUAGE plpgsql;
Using exec() then takes the form of a SELECT query with the appropriately generated query to be executed passed as the sole argument. We return the generated query text as an ease in auditing the actually executed results. Some examples: SELECT exec('CREATE ...read more... |
|
| |
|
|---|
| The cat is out of the proverbial bag. I originally planned to have a quiet roll out with a few close contributors but that has gone by the wayside. Now I am going to be pushing hard for people to test, beat on, object to, argue about, flame upon, scream at, praise and hopefully help us build out something that is truly useful for the FOSS Community. What am I blathering on about? FOSSExperts of course. FOSSExperts is a new site specifically engineered to allow FOSS developers to raise money for projects they are trying to develop. The idea stemmed from the very cool Kickstarter. With our focus obviously being on a different kind of creative. This is long overdue in the FOSS Community. There are a great deal of communities out there (LedgerSMB for example) that can use a place for their developers to try and raise funds for a specific feature. LedgerSMB just recently had a discussion on developing a Payroll module. Developing a Payroll module will be expensive for a ...read more... |
|
| |
|
|---|
| As a software engineer, you recognize at some point that there's much more to your career than dealing with code. Is it time to become a manager? Tell your boss he’s a jerk? Join that startup? Author Michael Lopp recalls his own make-or-break moments with Silicon Valley giants such as Apple, Netscape, and Symantec in Being Geek -- an insightful and entertaining book that will help you make better career decisions. |
|
| |
|
| Ссылки |
|---|
|
| Ссылки |
|---|
|
|
