php-general Digest 27 Nov 2011 19:28:18 -0000 Issue 7587
Topics (messages 315837 through 315840):
Re: [PHP-WIN] 5.3.9RC2 and 5.4RC2
315837 by: Pierre Joye
315838 by: Ferenc Kovacs
315839 by: Pierre Joye
Re: news and article posts in one table
315840 by: Larry Garfield
Administrivia:
To subscribe to the digest, e-mail:
[email protected]
To unsubscribe from the digest, e-mail:
[email protected]
To post to the list, e-mail:
[email protected]
----------------------------------------------------------------------
--- Begin Message ---
hi,
On Sat, Nov 26, 2011 at 9:43 AM, Tommy Pham <[email protected]> wrote:
> Hi everyone,
>
> 5.3.9RC2 works fine with all my apps so far. 5.4RC2 broke with sqlsvr
> and its PDO in addition to Wincache, which I've already brought to MS'
> attention.
Please report a bug at http://pecl.php.net/package/sqlsrv
http://pecl.php.net/package/wincache.
however I do not see what could be broken with 5.3.9, there is no
change that could affect these extensions.
> What's the estimated official release of 5.4?
See https://wiki.php.net/todo/php54
There is no deadline for the final release as we do not know yet all
possible issues we may find during the RCs phase.
Cheers,
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
--- End Message ---
--- Begin Message ---
On Sun, Nov 27, 2011 at 2:39 PM, Pierre Joye <[email protected]> wrote:
> hi,
>
> On Sat, Nov 26, 2011 at 9:43 AM, Tommy Pham <[email protected]> wrote:
> > Hi everyone,
> >
> > 5.3.9RC2 works fine with all my apps so far. 5.4RC2 broke with sqlsvr
> > and its PDO in addition to Wincache, which I've already brought to MS'
> > attention.
>
> Please report a bug at http://pecl.php.net/package/sqlsrv
> http://pecl.php.net/package/wincache.
>
> however I do not see what could be broken with 5.3.9, there is no
> change that could affect these extensions.
I think that he meant that only 5.4 is affected by those problems.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
--- End Message ---
--- Begin Message ---
hi,
I just uploaded two zip for sqlsrv and 5.4. I did not test them and
they are no official builds, only for testing purposes (so is 5.4 :).
you can find them at http://www.php.net/~pierre/
Cheers,
On Sat, Nov 26, 2011 at 9:43 AM, Tommy Pham <[email protected]> wrote:
> Hi everyone,
>
> 5.3.9RC2 works fine with all my apps so far. 5.4RC2 broke with sqlsvr
> and its PDO in addition to Wincache, which I've already brought to MS'
> attention. What's the estimated official release of 5.4? I can't
> wait for the feature session.upload_progress* in 5.4 which I need to
> do some testing as how I can implement that into my existing apps!!!
> That's just awesome!! Thanks for all your continuous hard work :)
>
> Platform: Win08R2/IIS7.5 SP1 with current patches running PHP as FastCGI.
>
> Applications:
> drupal, joomla, mediawiki, wordpress, and a few of my own :)
>
> Cheers,
> Tommy
>
> --
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
--- End Message ---
--- Begin Message ---
On 11/26/2011 09:45 PM, Paul M Foster wrote:
On Sat, Nov 26, 2011 at 01:26:49PM -0600, Tamara Temple wrote:
muad shibani<[email protected]> wrote:
i wanna to create one table that contains both news and articles posts,
they have similar columns like id, title, content, and date but they are
differ in one column = the source of news or article post
article has writers that have permanent names and pictures obtained from
another table called writers that supposed to be left joined with the news
table, while news posts simply have a source as text like AFP
or Reuters and so one.
How I can solve this ?
How you store things in tables can sometimes get a little tricky. One
way to approach this is with normalized tables and using joins in your
query like you are doing. To make this work, in your main entries table,
have a field that indicates what the entry type is. If you are doing one
select that gets both articles and news stories, having that extra field
can help you distinguish what type it is, and which fields contain data
in each record.
(cf: Wordpress wp_posts table for an example of how this is done. They
store posts, pages, and attachments in a single table this way. I can't
say if this is a better arrangement than keeping them in separate
tables.)
I've had to hack this table. It's a prime example of bad design. Take a
long look at the records of this table in an active blog, with a survey
of each of the fields and their values. You'll see what I mean.
Paul
The Drupal approach to this problem is to have a common table for all
"nodes" (our generic content object thingie), and then dependent tables
for type-specific stuff. So (over-simplifying):
node: id, title, type, created time, updated time, published (1 or 0)
field_body: node_id, delta, value
field_picture: node_id, delta, url
field_source: node_id, delta, url to reuters or whatever
field_writers: node_id, delta, writer name, url to writer picture
// etc.
That way, you can have the basic information all in one table and then
specific fields can be shared by some, all, or just one node type, and
all can be multi-value. It does mean loading up a full object is
multiple queries, but really, MySQL is fast. You don't need to
over-optimize your query count, and this gets you a well-normalized
database.
If you know in advance exactly what your types are going to be (in
Drupal they're user-configurable), you could simplify it to something like:
node: id, title, type, body. created time, updated time, published (1 or 0)
node_article: node_id, writer name, writer picture url
node_news: node_id, url to reuters or whatever
And you can still select on whatever you need. With a LEFT JOIN, you
can even get back all data on all articles of both types, and just have
lost of nulls in the result set for the off-record fields.
--Larry Garfield
--- End Message ---
