1
Garrath
Re: Module-Wide Cache
  • 2007/11/8 21:05

  • Garrath

  • Just popping in

  • Posts: 23

  • Since: 2007/6/11


Sorry for my bad english...

I think there is something wrong on your site.

If you look the html code you can see lot of \ (more than 60Ko )
If i remember, there is function to add and substract \ when you update or select data in SQL. Then if you have lot of \ on a data, there is a function to substract and this take a time.
And you take time because the data is great too...

Look your site description on admin panel :
Preferences Main »» Meta Tags and Footer
and Meta Description.



2
Garrath
Re: Support for SQL Parameterized queries ?
  • 2007/11/5 0:10

  • Garrath

  • Just popping in

  • Posts: 23

  • Since: 2007/6/11


it doesn't seam to work fine
http://doughboy.wordpress.com/2006/08/25/pdo-turbo-button/



3
Garrath
Re: Fixing the Xoops Tables in Mysql to Run Loads Faster
  • 2007/11/4 15:59

  • Garrath

  • Just popping in

  • Posts: 23

  • Since: 2007/6/11


??????

Desole je comprends pas ton intervention.

Je vais le dire en français. desole pour les autres

Cette table n'est la que pour faire la relation entre le group et les user. C'est betement une table de relation ce que l'on fait classiquement en relationnel. Elle n'a besoin que et uniquement des cles primaires des deux tables qu'elle met en relation.

=> linkid ne sert a rien fonctionnellement (c-a-d en terme de logique metier et meme de souplesse???) et techniquement, il prend de la place pour rien, et en plus ne force pas l'unicite des donnees (ce qui est dommage).
Et je vois pas en quoi ajouter un index primaire autoincrement sur ce genre de table de relation ajoute de la souplesse et de l'evolutivite...

Il me semble pas avoir dit qu'il ne fallait jamais utilise ce genre d'index autoincrement... (qu'on appelait cle techniques de mon temps qui sont justement tres pratique dans ce genre de table de relation car du coup on a que 2 champs si on avait du coller le nom, surnom etc... du user pfuuut)
Donc desole je comprend pas ton intervention... et j'ai beau relire mon intervention precedente je vois pas ce que me vaut cette intervention... et cela meme si je suis pas super bon en anglais.

Et perso j'adore les bases de donnees... je suis plus specialiste Oracle (de la version 5.0 a 8i apres bcq moins) que MySQL, et le relationnel (dans les bases ) ca a longtemps ete mon dada voir meme ma specialite .
Quand a la rapidite... plus tu auras de donnees et plus l'interet d'une base de donnees sera importante. Si tu as 5 donnee a gerer utilise un fichier plat c'est sur que cela sera plus rapide, si tu en as des tonnes y a pas photo prend une base de donnees (et si tu en as vraiment vraiment bcq y a des moteurs plus performants que d'autre...)

English Google Translation of the above:
Quote:
Sorry I do not understand your response.

I'll say it in French. sorry for the other

This table is only to make the relationship between the group and the user. It is foolishly a relationship table that is conventionally done in relationships. She does not need that and only primary keys of the two tables it links.

=> Linkid is useless functionally (ie in terms of logical profession and even flexibility??) And technically, it takes up space for nothing more and does not force the uniqueness of the data (which is a shame ).
And I do not see how to add a autoincrement primary index on this kind of relationship table adds flexibility and scalability ...

It seems to me not saying that you should never use this kind of index autoincrement ... (called key techniques that my time is just very handy in this type of relationship table becuase it has 2 fields if we had the paste name, nickname etc ... the user pfuuut)
So sorry I do not understand your response ... and I'm reading my previous response I do not see that this intervention is me ... and this even though I'm not super good at English.

And personally I love databases ... I am more specialist Oracle (version 8i after a 5.0 bcq less) than MySQL, and relational (in bases) ca has long been my hobby even see my specialty.
When was the rapidity ... get more and more data of the interest of a database is important. If you manage a given 5 uses a flat file that is on it will be faster if you have tons of picture taking is not a database (and if you have really really bcq engines are more efficient than other ...)



4
Garrath
Re: Fixing the Xoops Tables in Mysql to Run Loads Faster
  • 2007/11/4 13:14

  • Garrath

  • Just popping in

  • Posts: 23

  • Since: 2007/6/11


sorry for my bad english.

you can modify groups_users_link...

groups_users_link is not a data table is a relational one. this table it use to make relation between group and user. Then you just have groupid and uid in.

Actually in this table you have a linkid sequential column, and this column was the primary key. After you have an index with groupid and uid. First, there is a fonctionnal mistake in this index because is not define on unique index.
Second, what is interest of linkid column????

On this kind of table you just have only the key of the twice table. Is enough.

In this table you just have 2 column groupid and uid. Just this.
And you may put the twice column in primary key.

i Am agree there is no speed interest in this primary key with all column of table, but you have an interest on this data must be Unique.

By the way, we gain place because we have less index. then whe gain speed on update/insert/delete on this table, gain speed on select because the data is smaller etc...
//Suppression de l'index
ALTER TABLE groups_users_link DROP INDEX groupid_uid;
//Suppression de la cle autoincrement
ALTER TABLE groups_users_link DROP linkid;
//Creation de la cle primaire sur groupid et uid. Elle force l'unicite des lignes.
ALTER TABLE groups_users_link ADD PRIMARY KEY (groupiduid );



5
Garrath
Re: New functions in Xoops 2.0.18
  • 2007/11/3 13:19

  • Garrath

  • Just popping in

  • Posts: 23

  • Since: 2007/6/11


ok

What do you think about xml/xsl:fo with apache fo for make pdf? i just know it i don'tu use it now...

I think lot of think go to be on xml now for ajax etc...
With the same document in xml you can make html, pdf, chm etc...



6
Garrath
Re: New functions in Xoops 2.0.18
  • 2007/11/3 12:32

  • Garrath

  • Just popping in

  • Posts: 23

  • Since: 2007/6/11


Sorry for my bad english

Quote:

hervet wrote:
Hello,

What is planed for XOOPS 2.0.18 and is it possible to ask some new features like :

1/ Inclusion of tcpdf

what is it?

Quote:

hervet wrote:
2/ A new class to be able to use all the major WYSIWYG editors (Kiovi, FCK, TinyEditor etc). Some modules like Smartsection, CBB and News already have some code to manage this but copying into each module, each time is really boring

Yes it's a good way. I think to an interface (think php5 and OO) and that may be in core not in each module.
In general i think there may be have lot of general interface and people can be add class implements this interface and can be changed easily.
I'm on progress to put system like this on XOOPS for kernel's class.


Quote:

hervet wrote:
4/ etc

Yes...

I think to a log system like log4j it's a good thing for developpement with debug and i think after it's a good purpose for professional uses.

I found log4php but it's writing in php4...



7
Garrath
Re: Is anyone else sick of all this crap?
  • 2007/10/28 23:23

  • Garrath

  • Just popping in

  • Posts: 23

  • Since: 2007/6/11


Sorry for my bad english

this is not for you BlueStoking
Quote:

Stop 'political' discuss, Begin Technical subject... return to developpement...

this is in general way.


I think i can have technical discuss but not in english... but i can try to make an effort to be comprehensive for reader



8
Garrath
Re: Is anyone else sick of all this crap?
  • 2007/10/28 22:59

  • Garrath

  • Just popping in

  • Posts: 23

  • Since: 2007/6/11


I put here what i said yesterday
Quote:

Sorry for my bad english

I use Xoops, and i want to continue to use XOOPS because i don't want have the think to have lost time in use Xoops.
For that, XOOPS may be go ahead.
For me go ahead mean that XOOPS developpement continues...

But the problem is when i go to xoops.org, sourceforge etc... i see more 'political' discuss about XOOPS management, than discuss about XOOPS technical future.
Is not a good thing.

I don't want this 'political' discuss are in private area, it's better in public (for the knowlege of the community).
But i think there'll come a moment when you'll may stop and you'll be act something, and return to developpement. And that for the good of Xoops.
Don't forget that XOOPS is first a Software, and if developpement don't go, Xoops'll become a abandonware.
And after XOOPS dead, all 'political' discuss seem to be lost time. Who want to manage a foundation for a dead software?

https://xoops.org/modules/newbb/viewtopic.php?topic_id=61393&start=20#forumpost276357

You can see that i think like you Bassman...
And for BlueStocking i think there is a begining answer for your question...
Stop 'political' discuss, Begin Technical subject... return to developpement...



9
Garrath
Re: Support for SQL Parameterized queries ?
  • 2007/10/27 11:59

  • Garrath

  • Just popping in

  • Posts: 23

  • Since: 2007/6/11


For MySQL you can look this
http://www.php.net/manual/en/function.mysqli-prepare.php

you can understand more than my explication ( ) the difference between the actual way and this way.



10
Garrath
Re: Support for SQL Parameterized queries ?
  • 2007/10/27 11:41

  • Garrath

  • Just popping in

  • Posts: 23

  • Since: 2007/6/11


Sorry for my bad english
Quote:

Dave_L wrote:
Don't the XOOPS object and criteria classes already accomplish this?

No

Actually all query is construct when we need it.
All query are a constructed string.
We don't have some thing like this
SELECT * FROM table WHERE Id=? and param to put in after like we can have PRO*C (C with preprocessor Oracle)

We constuct a string like this
SELECT * FROM table WHERE Id=1
and this query is not the same at
SELECT * FROM table WHERE Id=2
then the SQL engine don't say it the same query then he calculate another time the optimize parse etc...

If you have this
SELECT * FROM table WHERE Id=? with param to passe the query is the same then we gain time of optimize parse.

It's work like that in Oracle.

Criteria just construct a String, it just put String from name of column and add string of the value you have, and add couple of column name, and value. Value is a print of $value
Like this :
colomnname = 'value' AND colomname2 = 'value2'

Criteria don't put
colomname = ?param1 AND colomname2 = ?param2




TopTop
(1) 2 3 »



Login

Who's Online

206 user(s) are online (133 user(s) are browsing Support Forums)


Members: 0


Guests: 206


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Mar 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits