Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 15 posts - 3,466 through 3,480 (of 7,398 total)
  • Author
    Posts
  • in reply to: Alter View Unreadable #25427
    peterlaursen
    Participant

    Let me add one detail!

    A view is 'frozen' at CREATE time!

    (and this is a SQL standard specification – not only a MySQL server implementation!)

    If you define “CREATE VIEW `someview` AS SELECT * FROM `sometable`;” — where `sometable` has columns a, b and c

    .. and add more columns (like d,e) to ´sometable` later, then `someview` will (and should!) only have columns a, b and c!

    So the original formatting at create time may not be valid at a later point.

    This is probably one detail that causes problems with using the original formatting!

    in reply to: Alter View Unreadable #25426
    peterlaursen
    Participant

    This is a server issue and not a SQLyog issue!

    SHOW CREATE VIEW does not return the original formatting.

    You can go to http://bugs.mysql.com and find lots of complaints about this.

    It is a silly issue, because the original formatting is stored (in a .frm file) actually, but the server does not use it.

    As SQLyog has no access to the file system, it cannot know the original formatting – only what the MySQL server returns for SHOW CREATE VIEW.

    in reply to: Objects Tab And Large Databases #25419
    peterlaursen
    Participant

    Usability suggestions are always welcome!

    I think in situations where:

    * tables a not very big

    * server is local

    .. the current design is most intuitive. As per your proposal user would manually need to 'refresh' and I think it would be an annoyance!

    However I realize that with big and remote tables it may not always be the case.

    Should we include an uption 'not to auto-update data area' when 'something' is selected in Object Browser? (I am not sure how easy that would be however!)

    in reply to: Question About Posible Bug #25285
    peterlaursen
    Participant

    If you create a view like

    “create view myview as select myfunction(..) as mycol”

    then the script will not restore because the function is not created vhen the view should be created. I only see the solution to have 2 dumps so that the function gets created in 1st dump and the view in 2nd.

    That will be possible from SQLyog 6.2

    in reply to: Saving Conversion Packages #25424
    peterlaursen
    Participant

    You can distribute the jobfile of course!

    I think you should test as soon as possible with the software. If not the discussion will be rather abstract.

    Now, I would assume that the table-structure of the two apps are so much different that data from more than one table onwill have to go into every table. So you will need the option to 'specify a query' from the first screen of the migration wizard.

    like “select tab1.a as new1, tab1.b as new2, tab2.x as new3, tab2.y as new4 from tab1, tab2”

    Also you will be able to use 'notifications service' to execute a maitenaince query after the import

    in reply to: Saving Conversion Packages #25422
    peterlaursen
    Participant

    I am sorry, but I do not have the slightest idea of what you are talking about!

    Do not expect us to know everyone of *.10.000's applications for MySQL – like 'PostNuke' and 'Joomla'!

    My best intuition tells me the answer that with the 'Migration Tool' you will be able to generate a job file that migrates one database to another and changes mapping/column definitions accordingly!

    in reply to: License Transfer? #25425
    peterlaursen
    Participant

    We do not use any kind kind of 'activation' model nor locks the registration details to specific hardware in other ways.

    If you have a binary/installer and corresponding registration details you can register on another computer as you like – but we request of course that you only have/use the # of installations as per your license!.

    in reply to: Objects Tab And Large Databases #25415
    peterlaursen
    Participant

    Thanks for your consideration.

    I think the comparison with Windows Explorer does not quite 'hold water'. SQLyog is a database client and will need to communicate with the server whenever something happens at the client side. In this case we send a USE statement.

    We will disucss this, but could you consider having two different connections with each of the databases specified for one connection?

    in reply to: Schema Designer #25414
    peterlaursen
    Participant

    don't worry .. your considerations are welcome.

    And I totally agree that the 'mouse-grey' background should be white when printing / saving as graphics!

    in reply to: Schema Designer #25412
    peterlaursen
    Participant

    And I meant DirextX and not ActiveX of course!

    in reply to: 6.13 Schema Designer #25373
    peterlaursen
    Participant

    Please verfiy the fix for this with 6.14 RC2.

    http://www.webyog.com/forums//index.php?showtopic=3640

    As regards the issue with the 'manage relationships' dialogue it is per design – only I became confused! The dialogue will display columns defined as FK. You can remove either by selecting it and pressing . However we will consider how to improve intuity in this respect!

    in reply to: Schema Designer #25411
    peterlaursen
    Participant

    1) zoom request has been asked a few times before allready. Current design does not allow for it. It will take some time!

    Basically the canvas currently is coded with pure win32 API coding (nothing like ActiveX or OpenGL for instance). Fundamentally it will require some kind of 'graphics layer' and a graphics processor of some kind.

    2) Can you explain why this is important?

    3)

    — > more beautiful … again you will need to detail what you do not like as of now!

    — > printable. Currently you can use a screengrabber. There are several that will let you capture a 'sub-window' (example: snag-it). We plan to implement 'save layout as graphics' soon.

    in reply to: Default Value For Int #25404
    peterlaursen
    Participant

    You can always change from a tinyint to a bigint for instance with ALTER TABLE!

    .. but what does 7 bytes of disk storage cost today? 🙂

    in reply to: Timestamp For "created" And "edited" #25409
    peterlaursen
    Participant

    you cannot use CURRENT_TIMESTAMP more than once in table definition.

    Try yourself:

    create table `TableName1` (

    `id` bigint UNSIGNED NOT NULL AUTO_INCREMENT ,

    `ts1` timestamp DEFAULT CURRENT_TIMESTAMP,

    `ts2` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,

    PRIMARY KEY (`id`))

    returns:

    Error Code : 1293

    Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause

    You will have to write current time to the second timestamp from the application using this table like

    UPDATE TABLE … SET `ts2` = now(); — 'now() is a handy synonym for CURRENT_TIMESTAMP only!

    .. you cannot solve this in the table definition! You may post a feature request to bugs.mysql.com, but I bet they heard it before!

    in reply to: Export Data To Excel Xml Trouble #25295
    peterlaursen
    Participant

    Please verify the fix for this issue with this build:

    ENTERPRISE link:

    http://www.webyog.com/downloads/betas/not_…QLyog614Ent.exe

    COMMUNITY link:

    http://www.webyog.com/downloads/betas/not_…d/SQLyog614.exe

Viewing 15 posts - 3,466 through 3,480 (of 7,398 total)